Axelar Network
Bug bounty on Immunefi axelar.network
- Top reward
- $500,000
- Top severity paid
- Critical
- Assets in scope
- 20
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $500,000
- for critical bugs, from $2,500.
- Report on Immunefi
- Submit through the program page.
- Paid by USDC
- Proof of identity needed to get paid.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Immunefi lists as the payout for each severity.
| Severity | Applies to | Relative size | Reward |
|---|---|---|---|
| Critical Blockchain | Blockchain |
|
$500,000 |
| Critical Contract | Contract |
|
$500,000 10% of funds at risk |
| High Blockchain | Blockchain |
|
$25,000 from $5,000 |
| High Contract | Contract |
|
$25,000 from $5,000 |
| Medium Blockchain | Blockchain |
|
$2,500 |
| Medium Contract | Contract |
|
$2,500 |
| Low Contract | Contract |
|
$1,000 |
| Low Blockchain | Blockchain |
|
$1,000 |
Scope
20 assets you may test.
Smart contracts 13
- https://bscscan.com/address/0x304acf330bbE08d1e512eefaa92F6a57871fD895
- https://bscscan.com/address/0x4268B8F0B87b6Eae5d897996E6b845ddbD99Adf3
- https://etherscan.io/address/0x4F4495243837681061C4743b74B3eEdf548D56A5
- https://etherscan.io/address/0x83a93500d23Fbc3e82B410aD07A6a9F7A0670D66
- https://etherscan.io/address/0xB5FB4BE02232B1bBA4dC8f81dc24C26980dE9e3C
- https://etherscan.io/token/0x467719aD09025FcC6cF6F8311755809d45a5E5f3
- https://ftmscan.com/address/0x1B6382DBDEa11d97f24495C9A90b7c88469134a4
- https://ftmscan.com/address/0x5e3C572A97D898Fe359a2Cea31c7D46ba5386895
- https://moonbeam.moonscan.io/address/0xCa01a1D0993565291051daFF390892518ACfAD3A
- https://polygonscan.com/address/0x6f015F16De9fC8791b234eF68D486d2bF203FBA8
- https://polygonscan.com/address/0x750e4C4984a9e0f12978eA6742Bc1c5D248f40ed
- https://snowtrace.io/address/0x5029C0EFf6C34351a0CEc334542cDb22c7928f78
- https://snowtrace.io/address/0xfaB550568C688d5D8A52C7d794cb93Edc26eC0eC
Source code 7
- https://github.com/axelarnetwork/axelar-cgp-solidity
- https://github.com/axelarnetwork/axelar-core
- https://github.com/axelarnetwork/axelar-gmp-sdk-solidity
- https://github.com/axelarnetwork/axelar-gmp-sdk-solidity/blob/main/contracts/governance/InterchainGovernance.sol
- https://github.com/axelarnetwork/interchain-token-service
- https://github.com/axelarnetwork/tofn/blob/main/src/ecdsa/mod.rs
- https://github.com/axelarnetwork/tofnd
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Axelar Network (via Immunefi)'s policy. "We" in these lines means the program, not this site.
While testing
-
Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
-
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 that are executed against project assets
-
Automated testing of services that generates significant amounts of traffic
-
Public disclosure of an unpatched vulnerability in an embargoed bounty
-
All Critical Blockchain/DLT and Smart Contract bug reports require a PoC to be eligible for a reward.
Not accepted
-
Any vulnerabilities discussed within the github issues below are considered vulnerabilities already known to Axelar, and will not be eligible for a reward
Summarised with AI from the program policy on Immunefi, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 57 minutes 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.
-
Reward terms
The reward table or payout terms were edited
-
Reward terms
The reward table or payout terms were edited
-
Reward terms
The reward table or payout terms were edited
-
Reward terms
The reward table or payout terms were edited
-
Scope added
https://moonbeam.moonscan.io/address/0x4F4495243837681061C4743b74B3eEdf548D56A5#code
-
Scope added
https://aurorascan.dev/address/0x304acf330bbE08d1e512eefaa92F6a57871fD895#code
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 immunefi.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Back to Explore Axelar Network Axelar Network is a decentralized interoperability network connecting all blockchains, assets and apps through a universal set of protocols and APIs. Arbitrum Avalanche BSC Base Blast Celo Centrifuge ETH Fantom Filecoin Fraxtal Kava Linea Mantle Moonbeam Optimism Polygon Scroll Blockchain Defi Maximum Bounty $500,000 Live Since 11 March 2022 Last Updated 11 November 2026 PoC Required KYC required Submit a Bug Information Scope Resources Rewards Axelar Network provides rewards in USDC on Arbitrum, Base , denominated in USD. Rewards by Threat Level Blockchain/DLT Critical Up to: $500,000 Primacy of Rules High Max: $25,000 Min: $5,000 Primacy of Rules Medium Flat: $2,500 Primacy of Rules Low Up to: $1,000 Primacy of Rules Smart Contract Critical Up to: $500,000 Primacy of Rules High Max: $25,000 Min: $5,000 Primacy of Rules Medium Flat: $2,500 Primacy of Rules Low Up to: $1,000 Primacy of Rules Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $500,000 Rewards Body Rewards are distributed according to the impact of the vulnerability based on the 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 Critical Blockchain/DLT and Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required. In addition to Immunefi’s Vulnerability Severity Classification System, Axelar Network classifies the following vulnerabilities as follows. In case of discrepancy, the one below will be followed. Critical Loss of funds of over or equal to $500,000 High Vulnerabilities that result in loss of funds of less than $500,000 Medium Vulnerabilities that result in loss of funds of less than $50,000 Low Vulnerabilities that result in loss of funds of less than $10,000 Any vulnerabilities discussed within the github issues below are considered vulnerabilities already known to Axelar, and will not be eligible for a reward: https://github.com/axelarnetwork/axelar-core/issues https://github.com/axelarnetwork/axelar-cgp-solidity/issues https://github.com/axelarnetwork/tofnd/issues https://github.com/axelarnetwork/tofn/issues Critical blockchain/ smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. There is no minimum reward for Critical smart contract vulnerabilities. Bug reports that are classified as High will be rewarded USD 5 000 and up to USD 25 000 at the Axelar team’s discretion. High impact rewards for the project bug bounty program are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. However, there is a minimum reward of USD 5 000 for High severity level, rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program. Only impacts that cause a loss of funds of over or equal to $500K are considered as Critical Axelar Network requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. We use a service provider, Jumio, to collect this information and will send you a link to the KYC application if your report is deemed eligible for bounties. The information needed is A piece of government issued photo ID such as passport or driver’s license A live webcam facial recognition scan to match biometrics with submitted photo ID The collection of this information will be done by the project team. Payouts are handled by the Axelar Network team directly and are denominated in USD. However, payouts are done in USDC . View impacts in scope Program Overview Axelar Network is a decentralized interoperability network connecting all blockchains, assets and apps through a universal set of protocols and APIs. For more information about Axelar Network, please visit https://axelar.network/ . KYC required The submission of KYC information is a requirement for payout processing. Proof of Concept Proof of concept is always required for all severities. Responsible Publication Category 3: Approval Required Prohibited Activities Default prohibited activities Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet 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 that are executed against project assets Automated testing of services that generates significant amounts of traffic Public disclosure of an unpatched vulnerability in an embargoed bounty Any other actions prohibited by the Immunefi Rules Feasibility Limitations The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total Assets in Scope 22