BTC24H Hack

TOTAL LOST $86K
Low Acces Control Exploit / Access Control polygon

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain polygon Incident surface
Recovered - No recovery reported
All-Time Rank #1553 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

Quick Summary

On December 16, 2024, BTC24H suffered an exploit on Polygon, leading to a loss of ~$85.7K.

Details of the Exploit

The vulnerability stemmed from poor access control, which enabled attackers to drain tokens from the contract without proper authorization. Exploiters took advantage of weak permissions to execute unauthorized transactions, resulting in the theft of approximately $85,700 worth of assets.

This is classified as a Access Control Attacks . Compare similar hacks →

Incident Report

Protocol / Project BTC24H
Date of Incident
Affected Chain(s) polygon
Attack Technique Acces Control Exploit / Access Control
Classification Protocol Logic / Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Access control
Affected Token BTC24H
Team Anonymous
Source Code Unverified

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of BTC24H's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Acces Control Exploit / Access Control audit checklist and test coverage

If you're auditing a protocol with similar architecture to BTC24H, these are the critical security checks that could have prevented this incident (December 2024).

  • Verify all logic paths related to Acces Control Exploit / Access Control are guarded by proper access controls and input validation - see the Access Control Attacks attack class for patterns
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Access Control Attacks

Proof-of-Concept Exploits

1 PoC available
poc-exploits - btc24h
$ BTC24H Logic Flaw

On-Chain Evidence & References

Sources & References

Learn to Prevent the Next BTC24H

The BTC24H hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Start Free Trial Browse Attack Library
Recreate exploit patterns safely Free Trial