NEAR Foundation Web (Low)
By Near Bug bounty on HackenProof near.foundation
- Top reward
- $2,500
- Top severity paid
- Critical
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $2,500
- for critical bugs.
- Report on HackenProof
- Submit through the program page.
- Replies within 5 days
- As the policy promises.
- Paid by NEAR token
- Proof of identity needed to get paid.
- No public write-ups
- Keep findings private.
Rewards
What HackenProof lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$2,500 |
- Response
-
Within 5 days
First Response 5d
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test, 3 excluded.
Web 1
- https://near.foundation
Out of scope (3)
- Assets that do not belong to the company
- Third-party services
- Vulnerabilities in third-party applications
Rules
What the policy asks of you, and the bug types it won't reward, quoted from NEAR Foundation Web (Low) (via HackenProof)'s policy. "We" in these lines means the program, not this site.
While testing
-
Make every effort not to damage or restrict the availability of products, services, or infrastructure
-
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
-
Don’t spam forms or account creation flows using automated scanners
-
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
-
Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
-
ONLY USE YOUR HackenProof ADDRESS (in case of violation, no bounty can be awarded)
Not accepted
-
Vulnerabilities in third-party applications
-
Best practices concerns
-
Social engineering, phishing, physical, or other fraud activities
-
Publicly accessible login panels without proof of exploitation
-
Reports that generated by scanners or any automated or active exploit tools
-
Denial of service (DoS/DDoS)
-
Theoretical issues
-
Moderately Sensitive Information Disclosure
-
Spam (sms, email, etc)
-
Missing HTTP security headers
-
Open redirects
-
Session fixation
-
User account enumeration
-
Clickjacking/Tapjacking and issues only exploitable through clickjacking/tap jacking
-
Descriptive error messages (e.g. Stack Traces, application or server errors)
-
Self-XSS that cannot be used to exploit other users
-
Login & Logout CSRF
-
Weak Captcha/Captcha Bypass
-
Lack of Secure and HTTP Only cookie flags
-
CSRF in forms that are available to anonymous users (e.g. the contact form)
-
OPTIONS/TRACE HTTP method enabled
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Reflected File Download (RFD)
-
Mixed HTTP Content
-
Manipulation with Password Reset Token
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 48 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from hackenproof.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Bug bounty Triaged by HackenProof NEAR Foundation Web (Low): Program info NEAR Foundation Web (Low) Company: Near Scope Review: 296081 Submissions: 86 Total rewards: $700 Reputation 100 points required KYC Required Program is: active now Live Submit report Program info Hackers 69 Reports 0 NEAR is the network for a world reimagined. Through simple, secure, and scalable technology millions are able to invent and explore new experiences. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Scope Search targets In scope Target │ Type │ Severity https://near.foundation/ Copy Web │ Low Focus Area IN-SCOPE VULNERABILITIES (WEB, MOBILE) We are interested in the following vulnerabilities: Business logic issues Payments manipulation Remote code execution (RCE) Injection vulnerabilities (SQL, XXE) File inclusions (Local & Remote) Access Control Issues (IDOR, Privilege Escalation, etc) Leakage of sensitive information Server-Side Request Forgery (SSRF) Cross-Site Request Forgery (CSRF) Cross-Site Scripting (XSS) Directory traversal Other vulnerability with a clear potential loss OUT OF SCOPE: WEB VULNERABILITIES Vulnerabilities found in out of scope resources are unlikely to be rewarded unless they present a serious business risk (at our sole discretion). In general, the following vulnerabilities do not correspond to the severity threshold: Vulnerabilities in third-party applications Assets that do not belong to the company Best practices concerns Recently (less than 30 days) disclosed 0day vulnerabilities Vulnerabilities affecting users of outdated browsers or platforms Social engineering, phishing, physical, or other fraud activities Publicly accessible login panels without proof of exploitation Reports that state that software is out of date/vulnerable without a proof of concept Reports that generated by scanners or any automated or active exploit tools Vulnerabilities involving active content such as web browser add-ons Most brute-forcing issues without clear impact Denial of service (DoS/DDoS) Theoretical issues Moderately Sensitive Information Disclosure Spam (sms, email, etc) Missing HTTP security headers Infrastructure vulnerabilities, including: Certificates/TLS/SSL-related issues; DNS issues (i.e. MX records, SPF records, DMARC records etc.); Server configuration issues (i.e., open ports, TLS, etc.) Open redirects Session fixation User account enumeration Clickjacking/Tapjacking and issues only exploitable through clickjacking/tap jacking Descriptive error messages (e.g. Stack Traces, application or server errors) Self-XSS that cannot be used to exploit other users Login & Logout CSRF Weak Captcha/Captcha Bypass Lack of Secure and HTTP Only cookie flags Username/email enumeration via Login/Forgot Password Page error messages CSRF in forms that are available to anonymous users (e.g. the contact form) OPTIONS/TRACE HTTP method enabled Host header issues without proof-of-concept demonstrating the vulnerability Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS Content Spoofing without embedded links/HTML Reflected File Download (RFD) Mixed HTTP Content HTTPS Mixed Content Scripts Manipulation with Password Reset Token MitM and local attacks Third-party services OUT OF SCOPE: MOBILE VULNERABILITIES Attacks requiring physical access to a user's device Vulnerabilities that require root/jailbreak Vulnerabilities requiring extensive user interaction Exposure of non-sensitive data on the device Reports from static analysis of the binary without PoC that impacts business logic Lack of obfuscation/binary protection/root(jailbreak) detection Bypass certificate pinning on rooted devices Lack of Exploit mitigations i.e., PIE, ARC, or Stack anaries Sensitive data in URLs/request bodies when protected by TLS Path disclosure in the binary OAuth & app secret hard-coded/recoverable in IPA, APK Sensitive information retained as plaintext in the device’s memory Crashes due to malformed URL Schemes or Intents sent to exported Activity/Service/Broadcast Receiver (exploiting these for sensitive data leakage is commonly in scope) Any kind of sensitive data stored in-app private directory Runtime hacking exploits using tools like but not limited to Frida/ Appmon (exploits only possible in a jailbroken environment) Shared links leaked through the system clipboard Any URIs leaked because a malicious app has permission to view URIs opened. Exposure of API keys with no security impact (Google Maps API keys etc.) Program Rules 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 Don’t spam forms or account creation flows using automated scanners 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: Near company is entitled to make the payment in their native NEAR token In case that your findings is valid you will be asked for KYC verification to proceed with payments Eligibility and Coordinated Disclosure 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, and any subsidiaries, are not eligible to participate in the Bug Bounty program. Disclosure Guidelines 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 Live since 29 Jun 2023 Published date 29 Jun 2023 Last updated 25 May 2026 Range of bounty $100 - $2,500 Severity Critical $1,500 - $2,500 High $750 - $1,500 Medium $250 - $750 Low $50 - $250 dApp Web @ola0 Verified 1 @VanStorek Verified 2 @allin Verified 3 @GoodHacker Verified 4 @S1r KYC 5 Response type Business days First Response 5d Triage Time 10d Reward Time 90d Resolution Time 25d