Mainnet Astar and Shiden (Included subfolders: runtime/)

Astar pallets (Included subfolders: frame/ and precompiles/)

The Shiden parachain on Kusama and the Astar parachain on Polkadot are both included in the assets-in-scope.

All source code can be found at [https://github.com/AstarNetwork/](https://github.com/AstarNetwork/). However, only those explicitly listed in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Astar Network that isn’t on this table but for which the impact is in the Impacts in Scope section, you are encouraged to submit it for the consideration of the project. This only applies to Critical impacts.

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.

Any network to shut down or otherwise not confirm new valid transactions for multiple blocks

Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)

Direct loss of funds

Permanent freezing of funds (fix requires hardfork)

Transaction/consensus manipulation

Unauthorized token minting

Governance compromise

Getting access to an identity that can lead to unauthorized access to system’s or user’s assets

Empty or freeze the contract's holdings (e.g. economic attacks, flash loans, reentrancy, MEV, logic errors, integer over-/under-flow)

Cryptographic flaws

Execute arbitrary system commands

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)

Taking down the application/website

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as: Changing registration information, commenting, voting, making trades, withdrawals, etc.

Subdomain takeover without already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as: Modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

GitHub misconfiguration leading to unauthorized change

Any unintended chain split or network partition

Any remotely-exploitable memory access, disk access, or persistent code execution. Attacks are restricted to the Stacks blockchain RPC/P2P ports

Blocking or modifying processes for governance or users from performing their tasks

Generating not handled on-chain errors - These actions can lead to blocking users or governance from accessing their assets or performing system functions

Token holders temporarily unable to transfer holdings

Transient consensus failures

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.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as: Email or password of the victim, etc.

Improperly disclosing confidential user information such as: Email address, phone number, physical address, etc.

High compute consumption by validator/mining nodes

A bug in the respective layer 1 network code that results in unintended smart contract behavior with no concrete funds at direct risk

DoS of greater than 30% of validator or miner nodes and does not shut down the network

Putting on-chain data into an unexpected state without interrupting the system or users from performing their tasks, e.g. generating redundant events, logs, etc

Block stuffing

Changing non-sensitive details of other users (including modifying browser local storage) w/o already-connected wallet interaction and with up to one click of user interaction, such as: Changing the first/last name of user, enabling/disabling notifications

Injecting/modifying the static content on the target application without Javascript (Reflected) such as: Reflected HTML injection, loading external site data

Open Redirect in H2O production’s environment

DoS of greater than 10% but less than 30% of validator or miner nodes and does not shut down the network

Underpricing transaction fees relative to computation time

Changing details of other users (including modifying browser local storage) w/o already-connected wallet interaction and with significant user interaction such as: Iframing leading to modifying the backend/browser state (must demonstrate impact with PoC)

Any impact involving a publicly released CVE without a working PoC

Temporarily disabling user to access target site, such as: Locking up the victim from login, cookie bombing, etc.

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All High and Critical Blockchain bug reports require a PoC and a suggestion for a fix to be eligible for a reward. All Medium and Low Blockchain bug reports require a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required. In specific cases, we keep the right to ask the whitehat to demonstrate PoC on the test environment provided by the Astar team to validate the impact of the report.

Critical vulnerabilities involving a direct loss of user funds, double spending, or the minting of tokens are capped at 10% of the economic damage, taking primarily into consideration the funds at risk or the amount of tokens that can be minted but also branding and PR considerations, at the discretion of the team. However, there is a minimum reward of __USD 50 000__. Consensus manipulation or governance compromise results in the full __USD 250 000__.

The final severity and reward amount are determined at the discretion of the Astar team by evaluating the funds at risk, possible impact, likelihood of attack, and other factors. If there are no funds at risk, the level of the bug may be downgraded or rejected.

A reward can only be provided if:
  - The bug wasn't reported before.
  - You do not disclose the bug to other parties or publicity until it's fixed by the Astar dev Team.
  - You didn't exploit the vulnerability or allow anyone else to profit from it.
  - You report a bug without any additional conditions or threats.
  - The investigation was NOT conducted with Ineligible methods or Prohibited Activities, as defined in this document.
  - You should reply to our additional questions regarding the reproduction of the reported bug (if they follow) within a reasonable time (up to 24h for Critical and up to 48hours for other levels of vulnerability)
  - When duplicate bug reports occur, we reward only the first one if it's provided with enough information for reproduction.
  - When multiple vulnerabilities are caused by one underlying issue, we will reward only the first reported.
  - The vulnerability is found in the runtime pallet of Astar (no tests, or modules that aren’t in runtime, e.g. live, can be considered as vulnerability).

Astar requires KYC and an invoice to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are Name, Address, Email. The collection of this information will be done by the Astar team. Astar may require additional KYC verification to be completed before payment can be released. Some countries are restricted when it comes to payments. This bug bounty program is only open to individuals who reside outside of the countries that are restricted by OFAC and by UNSC resolutions.

Payouts are handled by the __Astar Network__ team directly and are denominated in __USD__. However, payouts are done in __ASTR, SDN, USDC-ERC20, or USDT-ERC20__, subjected to Astar Network discretion.

Astar Network

Resources & Documentation