NEAR Intents: Bridges: Program info

Documentation:

• For more information on how to use the Intents ecosystem, please refer to the documentation.
• For technical information about the Verifier smart contract programming primitives (and other smart contracts here), please refer to the cargo documentation page.

Treasury Addresses

Reference: https://docs.near-intents.org/near-intents/treasury-addresses

IN-SCOPE VULNERABILITIES

The list is not limited to the following submissions but it gives an overview of what issues we care about:

• Stealing or loss of funds
• Unauthorized transaction
• Balance manipulation
• Contract execution flows
• Cryptographic flaws
• Unauthorized access to MPC key shares or signing capability
• Information disclosure of sensitive MPC state
• Bypass of threshold signature requirements
• Theft or permanent freezing of funds
• Cross-chain replay attacks enabling double-spending
• Light client verification bypass

OUT-OF-SCOPE VULNERABILITIES

• All vulnerabilities already discovered by Audit reports
• Unbounded gas or storage consumption
• Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
• Network-level DoS
• Vulnerabilities in the protocol that are unrelated to smart contract execution
• Wormhole guardian network (report to Wormhole)
• Social engineering or physical attacks including physical attacks on TEE hardware
• Mock attestation acceptance — TEE enforcement is in a grace period. Findings about non-TEE nodes being accepted are tracked separately and not considered vulnerabilities for this audit.
• Attacks requiring ≥ threshold colluding nodes
• NEAR chain attacks — validator collusion, chain reorgs, or finality failures.
• Test-only code paths — e.g. code gated behind #[cfg(test)] or test utilities not reachable in production.
• Non-default feature-only paths — e.g. findings that depend on network-hardship-simulation, dev-utils, test-utils, benchmark features, or similar non-production feature gates.
• Deployment / operational issues — misconfigured infrastructure, key management procedures, etc.
• Planned backup-service hard-launch design without code
• In-memory secret zeroization — e.g. key material is not wiped from memory after use
• RNG quality

If an impact can be caused to any other asset or service that isn’t in Scope, you are encouraged to submit it for the consideration by the project.

• Make every effort not to damage or restrict the availability of products, services, or infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Don’t access or modify other user data, localize all tests to your accounts
• Perform testing only within the scope
• Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
• In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
• Don’t break any law and stay in the defined scope
• Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
• Please note: company is entitled to make the payment in their native NEAR token vested over 1 year.
• In case that your finding is valid you might be asked for extra KYC verification to proceed with payments
• Perform testing on a private testnet wherever possible
• The total maximum reward for High and Critical severity bugs is capped at 10% of the funds that are practically affected by the discovered vulnerability: maxReward = min(10% TVL, maxSeverityBudget).

All findings are limited by top reward in their severity:

• Low - up to $1000
• Medium - up to $5000
• High - up to $10000
• Critical - up to $100000

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability
• Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
• ONLY USE YOUR HackenProof ADDRESS (in case of violation, no bounty can be awarded)
• Provide detailed but to-the point reproduction steps
• Employees, spouses, partners, or families of employees, and former employees of Pagoda, Near, and the Near Foundation, Aurora, Defuse Labs and any subsidiaries or contractors, are not eligible to participate in the Bug Bounty program.

• Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
• No vulnerability disclosure, including partial is allowed for the moment.
• Please do NOT publish/discuss bugs