Alchemix

Alchemix Finance is a future-yield-backed synthetic asset platform and community DAO. The platform gives you advances on your yield farming via a synthetic token that represents a fungible claim on underlying collateral in the Alchemix protocol.

For more information about Alchemix, please visit https://alchemix.fi/.

Primacy of Impact vs Primacy of Rules

Alchemix adheres to the Primacy of Rules. Learn more about report validity best practices here: Best Practice - Primacy of Impact vs Primacy of Rules.

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 Medium, High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. All Low Smart Contract bug reports require a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

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. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of USD 35 000 and a maximum of USD 300 000. For High vulnerability reports, the payouts will be primarily calculated as 10% of potential economic damage, primarily taking into account funds at risk but also PR and branding aspects, and bounded by the payout range for the vulnerability level.

The following vulnerabilities are not eligible for a reward:

• All vulnerabilities listed here https://github.com/code-423n4/2022-05-alchemix-findings/issues?q=is%3Aopen+is%3Aissue++-label%3A%22G+%28Gas+Optimization%29%22+-label%3A%22QA+%28Quality+Assurance%29%22 (succinct)
• All vulnerabilities listed here https://github.com/code-423n4/2022-05-alchemix-findings/issues?q=is%3Aopen+is%3Aissue+ (full)
• All vulnerabilities listed in Runtime Verification audit

Payouts are handled by the Alchemix team directly and are denominated in USD. However, payouts are done in ALCX.

All smart contracts of Alchemix can be found at https://github.com/alchemix-finance/v2-foundry. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. The in scope contracts can be found in the “src” folder, https://github.com/alchemix-finance/v2-foundry/tree/master/src, but excludes the “external/aave”, “mocks”, and “test” folder. All 3rd party code in any folder is also out of scope.

Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target.

If an impact can be caused to any other asset managed by Alchemix 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. This only applies to Critical and High impacts.

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)

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
• Best practice concerns
• Recently (less than 30 days) disclosed vulnerabilities in the supply chain
• Vulnerabilities affecting users of outdated browsers and/or platforms
• Social engineering or phishing attemps
• Vulnerabilities that require specific third party software on the user’s machine that is not part of the general usecase (i.e. browser + wallet add-on)
• Clickjacking/Tapjacking unless performed on a subdomain of alchemix.fi
• Tabjacking unless performed on a subdomain of alchemix.fi
• The forum hosted at forum.alchemix.fi
• The multisig hosted at multisig.alchemix.fi
• The staging environment hosted at staging.alchemix.fi

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