StarkNet is a validity rollup based on zk-STARK proofs. It operates as an L2 network over Ethereum, enabling any dApp to achieve scale for its computation – without compromising Ethereum's composability and security.

StarkNet is currently still in “alpha” stage. For more information about StarkNet, please visit https://starknet.io/ and https://docs.starknet.io/.

IN SCOPE

Smart Contract

Critical: Max: $250,000 Min: $15,000

• Direct theft of any user funds
• Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
• Permanent freezing of funds
• Protocol insolvency

Websites and Applications

Critical: Max: $10,000 Min: $5,000

• Execute arbitrary system commands

High Max: $2,500 Min: $1,250

• Injecting/modifying the static content on the target application without JavaScript (persistent), such as: HTML injection without JavaScript, Replacing existing text with arbitrary text, Arbitrary file uploads, etc

Prohibition On Simultaneous Submissions

Researchers are not permitted to submit the same vulnerability report simultaneously on multiple platforms. Violation of this rule will result in the blocking of the researcher's account.

OUT OF SCOPE

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 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/tapjacking

• 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 clear security impact

• 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

• Response manipulations without demonstration of system state change

• Impacts requiring attacks that the reporter has already exploited themselves, leading to damage

• Theoretical vulnerabilities without any proof or demonstration

• Old compiler version

• The compiler version is not locked

• Vulnerabilities in imported contracts

• Code style guide violations

• Redundant code

• Gas optimizations

• Best practice issues

• Vulnerabilities that can be exploited through front-run attacks only

• Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
• 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
• All communication regarding the program must take place exclusively through the HackenProof platform. Contacting the project team directly through support channels, social media, or any other external communication channels is strictly prohibited. Researchers who violate this rule may be disqualified from the program and may face account suspension.

• 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.
• Platform-Only Disclosure: Disclosure is only possible through the HackenProof Disclosure function.
• Researchers may request disclosure (Limited or Full) within the report ticket;
• We reserve the right to approve, redact, or deny disclosure requests at our sole discretion.
• Mutual Required: Any publication requires explicit mutual agreement. Reports must remain Private until the status is officially changed to "Public" on the HackenProof platform by the team.

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.
• You must not be a former or current employee of us or one of its contractor.
• ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
• Provide detailed but to-the point reproduction steps.
• AI-generated reports without runable PoC are not accepted under this program.