Arkham
Program Overview
Arkham is a crypto intelligence platform that enables users to see the organizations and people behind crypto wallet addresses & learn about their activities.
For more information about Arkham, please visit https://arkhamintelligence.com
Arkham provides rewards in ARKM. For more details about the payment process, please view the Rewards by Threat Level section further below.
Responsible Publication
Arkham adheres to category 3: Approval Required. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
Primacy of Impact vs Primacy of Rules
Arkham adheres to the Primacy of Impact for the following severity levels:
- Web/App - Critical
- Web/App - High
- Web/App - Medium
Arkham adheres to the Primacy of Impact for the following impacts:
- Web/App - Low - Temporarily disabling user to access target site
If an impact is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi.
Testnet and mock files are not covered under the Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program.
Known Issue Assurance
Arkham commits to providing Known Issue Assurance to bug submissions through their program. This means that Arkham will either disclose known issues publicly or at the very least privately via a self-reported bug submission in order to allow for a more objective and streamlined mediation process to prove that an issue is known. Otherwise, assuming the bug report itself is valid, it would result in the bug report being considered in-scope and due 100% of the reward with respect to the bug bounty program terms.
Immunefi Standard Badge
Arkham has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to our best practices.
Rewards by Threat Level
Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.
Reward Calculation for Critical Level Reports
For critical Web/App bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 20 000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 10 000 is to be rewarded in order to incentivize security researchers against withholding a bug report.
Repeatable Attack Limitations
In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable.
Public Disclosure of Known Issues
Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program.
- Old referral links exposing user emails
- User can share their private entities and dashboards by sharing the URL (this is a feature not a bug)
Previous Audits
Arkham has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- https://certificate.quantstamp.com/full/arkham-intelligence/751c39ed-1bff-4047-9082-24df856ab24e/index.html
- https://certificate.quantstamp.com/full/arkham-intel-exchange-bounty-contract/f86ecee0-d44f-48c3-80e9-e8570e2abadb/index.html
Proof of Concept (PoC) Requirements
A PoC is required for the following severity levels:
- Web/App - Critical
- Web/App - High
- Web/App - Medium
- Web/App - Low
All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.
Reward Payment Terms
Payouts are handled by the Arkham team directly and are denominated in USD. However, payments are done in ARKM.
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. For avoidance of doubt, if the reward amount is USD 5 000 and the average price is USD 1.75 per token, then the reward will be 2857.142857 units of that token.
Websites and Applications
- Critical
- Level
- USD $10,000 to USD $20,000
- Payout
- High
- Level
- USD $10,000
- Payout
- Medium
- Level
- USD $5,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Assets in scope
- Websites and Applications - APIType
- Websites and Applications - PlatformType
- Websites and Applications - WebsiteType
- Primacy Of ImpactTargetWebsites and ApplicationsType
Documentation for the assets provided in the table can be found at https://arkhamintelligence.notion.site/Quick-Start-Guide-Read-First-628d5abcdc4d47bc8a2b1eb75f3f9509.
Unless explicitly listed, only pages of the web/app assets in addition to the direct link are considered in-scope of the bug bounty program. Other subdomains are not considered as in-scope. However, for subdomain takeovers that lead to an impact on the in-scope asset, please refer to our page about Reported Subdomain Takeovers.
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
Websites and Applications
- Execute arbitrary system commandsCriticalImpact
- Retrieve sensitive data/files from a running server such as: /etc/shadow, database passwords, blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)CriticalImpact
- Taking down the application/websiteCriticalImpact
- Taking down the NFT URICriticalImpact
- 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.CriticalImpact
- Changing the NFT metadataCriticalImpact
- Subdomain takeover with already-connected wallet interactionCriticalImpact
- Direct theft of user fundsCriticalImpact
- Malicious interactions with an already-connected wallet such as: Modifying transaction arguments or parameters, Substituting contract addresses, Submitting malicious transactionsCriticalImpact
- 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.HighImpact
- 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.HighImpact
- Improperly disclosing confidential user information such as: Email address, Phone number, Physical address, etc.HighImpact
- Subdomain takeover without already-connected wallet interactionHighImpact
- Changing non-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: Changing the name of user, Enabling/disabling notificationsMediumImpact
- Injecting/modifying the static content on the target application without Javascript (Reflected) such as: Reflected HTML injection, Loading external site dataMediumImpact
- Redirecting users to malicious websites (Open Redirect)MediumImpact
- Unintentional leakage of private information (such as private labels, tracked addresses, user email and connected wallet addresses)MediumImpact
- Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction such as: Iframing leading to modifying the backend/browser state (demonstrate impact with PoC)LowImpact
- Temporarily disabling user to access target site, such as: Locking up the victim from login, Cookie bombing, etc.LowImpact
Out of Scope & Rules
These impacts are out of scope for this bug bounty program.
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 (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
- 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
Web/App
- Theoretical impacts without any proof or demonstration
- Impacts involving attacks requiring physical access to the victim device
- Impacts involving attacks requiring access to the local network of the victim
- Reflected plain text injection (e.g. url parameters, path, etc.)
- This does not exclude reflected HTML injection with or without JavaScript
- This does not exclude persistent plain text injection
- Any impacts involving self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (e.g. logout CSRF)
- Impacts related to missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure, such as IPs, server names, and most stack traces
- Impacts causing only the enumeration or confirmation of the existence of users or tenants
- Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- Impacts that only require DDoS
- UX and UI impacts that do not materially disrupt use of the platform
- Impacts primarily caused by browser/plugin defects
- Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
- Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
- SPF/DMARC misconfigured records
- Missing HTTP Headers without demonstrated impact
- Automated scanner reports without demonstrated impact
- UI/UX best practice recommendations
- Non-future-proof NFT rendering
The following activities are prohibited by this bug bounty program:
- 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