Paradex Bug Bounty Program

Paradex is an advanced perp DEX built on a ZK-rollup Layer 2, combining self-custodial security with CEX-like performance through deep liquidity, portfolio margin capabilities, and innovative features like trading privacy and retail price improvement.

For more information about Paradex, please visit https://www.paradex.trade/

Rewards

Paradex provides rewards in USDC on ETH, denominated in USD.

Rewards by Threat Level

Smart Contract

• Critical: Max $500,000, Min $25,000
• High: Max $15,000, Min $10,000
• Medium: Flat $4,000
• Low: Flat $2,000

Websites and Applications

• Critical: Max $20,000, Min $10,000
• High: Flat $3,000
• Medium: Flat $1,000
• Low: Flat $500

Reward Calculation

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.

Critical Level Smart Contract Bugs

For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 500,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. A minimum reward of USD 25,000 is awarded to incentivize security researchers against withholding a critical bug report.

Repeatable Attack Limitations

• If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. The reward amount will depend on the severity of the impact and the funds at risk.
• For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.

High Level Smart Contract Reports

• High vulnerabilities concerning theft/permanent freezing of unrealized PnL are rewarded within a range of $10,000 to $15,000 depending on the funds at risk, capped at the maximum high reward.
• In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24 hours that the funds are temporarily frozen, up until the max cap of the high reward.

Critical Web/Apps Bug Reports

Critical web/apps bug reports will be rewarded with $20,000 only if the impact leads to:

• A loss of funds involving an attack that does not require any user action
• Private key or private key generation leakage leading to unauthorized access to user funds

All other impacts that would be classified as Critical are rewarded a flat amount of $10,000.

Reward Payment Terms

Payouts are handled by the Paradex team directly and are denominated in USDC on ETH. The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.

Program Details

Primacy of Impact vs Primacy of Rules

Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.

When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.

If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.

Eligibility & Requirements

KYC Required

The submission of KYC information is a requirement for payout processing. Participants must adhere to the Eligibility Criteria.

Proof of Concept

Proof of concept is always required for all severities.

Responsible Publication

Category 3: Approval Required

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 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.

Immunefi has developed 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?

Known Issues

Websites and Applications

• All issues from Pathfinder RPC dependency (Last Updated: 25 August 2025)
• All issues from Juno RPC dependency (Last Updated: 25 August 2025)

Smart Contract

• Acknowledged issues from Cairo Security Clan Audit (Last Updated: 25 August 2025)

Audits

• All Audits: https://docs.paradex.trade/security/audit-pentests (Completed: 25 August 2025)