Attackathon | Stacks II-logo

Attackathon | Stacks II

Stacks is a Bitcoin L2 enabling smart contracts & apps with Bitcoin as the secure base layer. This Attackathon focuses on Stacks’ sBTC upgrade.

Bitcoin
Stacks
L2
Rust
Clarity

Evaluating

16d: 13h remaining
Reward Pool
$250,000
Start Date
24 February 2025
End Date
27 March 2025
Rewards Token
STX
Lines of Code
38,000
  • Triaged by Immunefi

  • PoC required

  • KYC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Blockchain/DLT - WSTS GitHub repository. Refer to `rev` as specified in the WSTS entry of the Cargo.toml file in the sBTC repository. Vulnerabilities related to WSTS will only be considered in scope if they can be exploited in sBTC.
Added on
26 February 2025
Target
Type
Blockchain/DLT - sBTC GitHub repo
Added on
24 February 2025
Target
Type
Smart Contract - sBTC GitHub repo
Added on
24 February 2025

Impacts in Scope

Previous Audits

Stacks’s completed audit reports can be found at https://stacks.org/audits . As well as the sBTC audit here, which the 3rd audit report from the top of the list.

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.

The Stacks team will label known issues with the label 'immunefi-scope' ( https://github.com/stacks-network/sbtc/labels/immunefi-scope ) to allow security researchers to easily filter them out.

Private Known Issues Reward Policy

Private known issues, meaning known issues that were not publicly disclosed, are valid for a reward.

Stacks’ Feasibility Limitations

In addition to our standard feasibility limitations, the following also apply:

  • Non-Criticals which can be objectively determined to only be able to affect <1% of users may be downgraded by 1 severity.
  • Non-Critical impacts that are dependent on execution to have a malicious signer involved, may be downgraded by 1 severity level.
  • Vulnerabilities related to WSTS will only be considered in scope if they can be exploited in sBTC.
Severity
Critical
Title

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Severity
Critical
Title

Permanent freezing of funds

Severity
Critical
Title

Protocol insolvency

Severity
Critical
Title

Direct loss of funds

Severity
Critical
Title

Permanent freezing of funds (fix requires hardfork)

Severity
High
Title

Theft of unclaimed yield

Severity
High
Title

Permanent freezing of unclaimed yield

Severity
High
Title

Network not being able to confirm new transactions (total network shutdown)

Severity
High
Title

Unintended permanent chain split requiring hard fork (network partition requiring hard fork)

Severity
High
Title

Unintended chain split (network partition)

Severity
High
Title

Temporary freezing of funds for at least 24h

Severity
Medium
Title

A bug in the respective layer 0/1/2 network code that results in unintended smart contract behavior with no concrete funds at direct risk

Out of scope

Default Out of Scope and rules

Blockchain/DLT 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