![Astar Network-logo](/_next/image/?url=https%3A%2F%2Fimages.ctfassets.net%2Ft3wqy70tc3bv%2F14P174mW7atHe0iqI2UmE8%2Fb47c08fa562ebe74aaff6b179e371d00%2FAstar_Network_logo.jpeg&w=128&q=75)
Astar Network
Astar Network supports the building of dApps with EVM and WASM smart contracts and offers developers true interoperability with cross-consensus messaging and cross-virtual machines. Astar’s unique Build2Earn model empowers developers to get paid through a dApp staking mechanism for the code they write and dApps they build.
ETH
Polkadot
Defi
Crosschain Liquidity
L2
Staking
JavaScript
Rust
Solidity
Typescript
Maximum Bounty
$250,000Live Since
31 May 2022Last Updated
08 April 2024PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Target
Type
Added on
Target
Type
Added on
Impacts in Scope
Critical
Any network to shut down or otherwise not confirm new valid transactions for multiple blocks
Critical
Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)
Critical
Direct loss of funds
Critical
Permanent freezing of funds (fix requires hardfork)
Critical
Transaction/consensus manipulation
Critical
Unauthorized token minting
Critical
Governance compromise
Critical
Getting access to an identity that can lead to unauthorized access to system’s or user’s assets
Critical
Empty or freeze the contract's holdings (e.g. economic attacks, flash loans, reentrancy, MEV, logic errors, integer over-/under-flow)
Critical
Cryptographic flaws
Critical
Execute arbitrary system commands
Critical
Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)
Out of scope
Program's Out of Scope information
GitHub and other cloud platforms misconfiguration are considered web/app vulnerabilities.
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist)
- Spamming
- Any physical attacks against Astar property, or employees
- Phishing or other social engineering attacks against our Astar’s employees
- Any attack requiring successful phishing or another scam to be executed
- Astar network footprints such as employee email addresses, subdomains, whois info
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection ex: url parameters, path, etc.
- This does not exclude reflected HTML injection with or without javascript
- This does not exclude persistent plain text injection
- Self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (ex: logout CSRF)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
- All vulnerabilities and attack methods that are listed in OWASP https://owasp.org/www-community/attacks/
- Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
The following activities are prohibited by this bug bounty program:
- Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
- Any testing with pricing oracles or third party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty