Filecoin is a decentralized storage network designed to store humanity's most important data. We invite security researchers to participate in our bug bounty program and help us secure the broader Filecoin ecosystem.
Runnable PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Protocol-level bug that causes a general breakage of all contracts deployed on the chain
Direct loss of funds belonging to a party other than the attacker, moved without that party's authorization
Unintended permanent chain split requiring hard fork (network partition persisting after affected nodes restart on patched binaries, reconcilable only by hard fork or state rollback)
Permanent freezing of funds (fix requires hardfork; funds belong to a party other than the attacker and are recovered by no protocol mechanism, node upgrade, hot patch, or operator action)
Permanent total chain halt where no new messages can be included in any tipset, the halt does not clear on restart of unmodified nodes or by a hot patch applied by operators, and recovery requires a hard fork or a rollback of chain state already produced or finalized
Protocol-level bug that enables tricking contracts into sending funds to an address their own code and state do not authorize
Protocol-level bug preventing contracts from using their funds
Unintended chain split (Network partition) with localized impacts (which would require hard fork but doesn't affect the chain as whole, and the canonical chain continues to advance)
Transient consensus failures (Temporary halt in transactions leading to consensus failure, restored without hard fork or state rollback, on restart of unmodified nodes, or via a hot patch applied individually by operators)
Protocol-level bug causing the inability to deploy new smart contracts network wide
Protocol-level bug rendering a single contract the attacker does not control permanently unusable after the exploit (i.e. contract bricked)
Inability to propagate new transactions (limited to a fraction of the network), persisting after attack traffic stops or indefinitely sustainable, demonstrated on the Filecoin Audit Kit devnet running a mainnet-equivalent configuration at default resource limits.
Out of scope
All submissions must include a working proof of concept demonstrated against a running local devnet. Use the Filecoin Audit Kit (https://github.com/FilecoinFoundationWeb/filecoin-audit-kit) to set up your environment it provides one-command devnet setups for Lotus (setup.sh) and Boost (setup-boost.sh).
The following are out of scope and will be closed without review:
- Unit tests (_test.go, #[test], or equivalent) as the sole PoC unit tests do not exercise consensus, networking, or state sync, which are the layers where exploitability must be proven
- Fuzzer crash outputs without a devnet reproduction showing the crash is reachable from an external input on a running node
- Static analysis or linter findings without demonstrated exploitability on a devnet
- Theoretical writeups without runnable exploit code
- Screenshots or video recordings as sole evidence (acceptable as supplements, not replacements)
- AI/LLM-generated reports not validated by the researcher against a running devnet
A valid submission must include: the Audit Kit setup and version used, any source modifications as diffs, runnable exploit code, execution output, and impact evidence (crash logs, state diffs, or chain behavior). See the PoC Submission Requirements for the full expected structure.
Blockchain/DLT specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers