Attackathon | Movement Labs
Movement Labs is a core contributor to Movement Network, a Move-based blockchain network that settles to Ethereum and creates safer execution environments by way of move.
Live
Triaged by Immunefi
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
No Runnable PoC Code Required
For this program, runnable PoC code is not required. Whitehats are instead required to write a step-by-step explanation of the PoC and impact. For more information, please read Audit Competition Proof-of-Concept Rules.
Asset Accuracy Assurance
Bugs found on assets incorrectly listed in-scope are valid.
Previous Audits
Movement Labs’s completed audit reports can be found here:
- https://1247499478-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBMbDkZsgQosju3BU30VN%2Fuploads%2FIw6F6sO75Gl3oOa9D6kD%2Fmeridian_audit_final.pdf?alt=media&token=f5ab2581-9407-4b2b-93d2-e7c61760cdbd
- https://docs.canopyhub.xyz/audits/audit-reports
- https://drive.google.com/file/d/1nTg57yVLay1TrBbB3HnEoQ_ElQ0_rScL/view?usp=sharing
- https://docs.echelon.market/echelon-v1/security/audit-reports
- https://github.com/movementlabsxyz/layerzero-devtools/issues
- https://github.com/movementlabsxyz/aptos-core/issues
- https://github.com/movementlabsxyz/movement/issues
- https://github.com/aptos-labs/aptos-core/issues
Unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Public Disclosure of Known Issues
Bug reports for publicly disclosed bugs are not eligible for a reward.
Private Known Issues Reward Policy
Private known issues, meaning known issues that were not publicly disclosed, are valid for a reward.
Mainnet AC (Audit Competition) Bug Fix Policy
The project may make bug fixes during the competition.
- Fixed bugs immediately become out of scope once the fix is public.
- Duplicate submissions of a bug are only valid if they’re submitted before the fix is public.
All project made bug fixes immediately become in scope for the mitigation competition once the fix is public, including fixes to bugs found independently of SRs.
Read our full mainnet AC rules for more info [ZendeskArticleLinkFor - TBD].
KYC Requirement
Movement Labs requires KYC information to pay for bug submissions. The following information will be required:
- Full name
- Date of birth
- Proof of address (either a redacted bank statement with address or a recent utility bill)
- Copy of Passport or other Government issued ID
Security researchers are required to submit KYC within 14 days of KYC being requested, else their rewards may be forfeited. Immunefi may make exceptions due to extenuating circumstances.
Eligibility Criteria
Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
- On OFACs SDN list
- Official contributor, both past or present
- Employees and/or individuals closely associated with the project
- Security auditors that directly or indirectly participated in an audit review of the code in scope (Such auditors may still participate in this program only if they receive project permission)
Direct loss of funds
Permanent freezing of funds (fix requires hardfork)
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Network not being able to confirm new transactions (total network shutdown)
Unintended chain split (network partition)
Temporary freezing of network transactions by delaying one block by 500% or more of the average block time of the preceding 24 hours beyond standard difficulty adjustments
Causing network processing nodes to process transactions from the mempool beyond set parameters
RPC API crash affecting programs with greater than or equal to 25% of the market capitalization on top of the respective layer
Permanent freezing of funds
Increasing network processing node resource consumption by at least 30% without brute force actions, compared to the preceding 24 hours
Shutdown of greater than or equal to 30% of network processing nodes without brute force actions, but does not shut down the network
Out of scope
Smart Contract 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