Skip to content

NEAR Web

By Near Bug bounty on HackenProof near.org

Accepting reports KYC to get paid Web dApp
Top reward
$50,000
Top severity paid
Critical
Assets in scope
3
Public CVEs
0
Last change

At a glance

What to know before you start testing.

Pays up to $50,000
for critical bugs.
Report on HackenProof
Submit through the program page.
Replies within 3 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 Reward
Critical $50,000
Response
Within 3 days First Response 3d

Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

3 assets you may test, 13 excluded.

Domains 2

  • docs.near.org
  • near.org

Wildcard domains 1

  • *.near.org
Out of scope (13)
  • awx.near.org
  • global-testnet.near.org
  • gov.near.org
  • grafana.near.org
  • jupyter.near.org
  • nayduck.near.org
  • prometheus.near.org
  • *.betanet.near.org
  • *.cn.near.org
  • *.internal.near.org
  • *.mainnet.near.org
  • *.shardnet.near.org
  • *.testnet.near.org

Rules

What the policy asks of you, and the bug types it won't reward, quoted from NEAR Web (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
  • 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
  • Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com

Not accepted

  • 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
  • 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 HTTPOnly cookie flags

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 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Scope removed

    wiki.near.org

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search 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 Web: Program info NEAR Web Company: Near Scope Review: 332980 Submissions: 328 Total rewards: $302,980 Reputation 100 points required KYC Required PoC Required Program is: active now Live Submit report Program info Hackers 180 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 near.org Copy Web │ High docs.near.org Copy Web │ Medium *.near.org Copy Web │ Low Out of scope Out of scope Target │ Type │ Severity gov.near.org Copy Web │ None *.mainnet.near.org Copy Web │ None *.testnet.near.org Copy Web │ None *.shardnet.near.org Copy Web │ None *.internal.near.org Copy Web │ None prometheus.near.org Copy Web │ None Show all targets Focus Area Only main website domain takeover can be considered as critical severity issue. IN-SCOPE VULNERABILITIES WEB VULNERABILITIES 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 Issues discovered in subdomain are capped by Low severity, and bounty in amount for 100-500$ 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 HTTPOnly 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 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 20 Feb 2023 Published date 10 May 2023 Last updated 19 Oct 2026 Range of bounty $100 - $50,000 Severity Critical $20,000 - $50,000 High $10,000 - $20,000 Medium $5,000 - $10,000 Low $100 - $1,000 dApp Web @BrunoModificato KYC Verified 1 st @stokes 2 @z0rs Verified 3 @serhiisecurity KYC Verified 4 @0xj3st3r KYC Verified 5 Response type Business days First Response 3d Triage Time 3d Reward Time 90d Resolution Time 14d