Chain

Chain is a blockchain based technology company on a mission to enable a smarter and more connected economy. We build cryptographic ledgers that underpin breakthrough financial products and services. Powered by Sequence, our ledger as a service platform.

For more information about Chain, please visit https://www.chain.com/.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. All Blockchain/DLT bug reports require a PoC and a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

Critical blockchain/DLT vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 150 000.

Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 150 000.

Payouts are handled by the Chain team directly and are denominated in USD. However, payouts are done in USDC, XCN, USDT and ETH, with the choice of the ratio at the discretion of the team.

Blockchain/DLT

Smart Contract

Websites and Applications

All smart contracts of Chain can be found at https://github.com/chain. However, only those in the Assets in Scope table’s located in the main branch are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Chain that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)
• Vulnerabilities affecting Timelock contracts that are not mentioned in Impacts in Scope section

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Centralization risks

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Attacks requiring physical access to the victim device
• Attacks requiring access to the local network of the victim
• Reflected plain text injection ex: url parameters, path, etc.
  • This does not exclude reflected HTML injection with or without javascript
  • This does not exclude persistent plain text injection
• Self-XSS
• Captcha bypass using OCR without impact demonstration
• CSRF with no state modifying security impact (ex: logout CSRF)
• 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
• Vulnerabilities used only to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Feature requests
• Issues related to the frontend without concrete impact and PoC
• Best practices issues without concrete impact and PoC
• Vulnerabilities primarily caused by browser/plugin defects
• Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
• Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
• Rate limiting
• Dangling IPs
• Exposed login panels
• Highly speculative reports about theoretical damage
• Open ports without an accompanying proof-of-concept demonstrating vulnerability
• Ability to take over social media groups and pages (Twitter, Telegram, etc)
• Reports that state that software is out of date/vulnerable without a proof-of-concept
• Unchained open redirects
• Protocol mismatch
• Ability to send push notifications/SMS messages/emails without the ability to change content
• Unclaimed pages/repositories/buckets that are not in public Chains scripts (Github, AWS etc)
• Sequence (Subdomain sequence.chain.com)

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• 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
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty
• Interact with accounts you do not own
• Upload shells or create a backdoor of any kind.
• Attempt to extract, download, or otherwise exfiltrate data that may have PII or other sensitive data other than your own.
• Brute force credentials or guess credentials to gain access to systems.
• Change passwords of any account that is not yours or that you do not have explicit permission to change. If ever prompted to change a password of an account you did not register yourself or an account that was not provided to you, stop and report the finding immediately.
• Publicly disclose a vulnerability without our explicit review and consent.