Documentation for the assets provided in the table can be found at [https://arkhamintelligence.notion.site/Quick-Start-Guide-Read-First-628d5abcdc4d47bc8a2b1eb75f3f9509. ](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.](https://immunefisupport.zendesk.com/hc/en-us/articles/14352199704593-Reported-Subdomain-Takeovers)

Arkham is a crypto intelligence platform that enables users to see the organizations and people behind crypto wallet addresses & learn about their activities.

Execute arbitrary system commands

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)

Taking down the application/website

Taking down the NFT URI

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.

Changing the NFT metadata

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as: Modifying transaction arguments or parameters, Substituting contract addresses, Submitting malicious transactions

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.

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.

Improperly disclosing confidential user information such as: Email address, Phone number, Physical address, etc.

Subdomain takeover without already-connected wallet interaction

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 notifications

Injecting/modifying the static content on the target application without Javascript (Reflected) such as: Reflected HTML injection, Loading external site data

Redirecting users to malicious websites (Open Redirect)

Unintentional leakage of private information (such as private labels, tracked addresses, user email and connected wallet addresses)

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)

Temporarily disabling user to access target site, such as: Locking up the victim from login, Cookie bombing, etc.

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-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](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.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-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.


Arkham

Resources & Documentation