SBI Crypto Hack
Incident Overview
On September 24, 2025, SBI Crypto, a mining pool subsidiary of Japan's SBI Holdings, suffered a theft of approximately $24 million across five blockchains: Bitcoin, Ethereum, Litecoin, Dogecoin, and Bitcoin Cash. The attack went unnoticed for seven days until blockchain detective ZachXBT flagged the incident on October 1st, with stolen funds laundered through instant exchanges and Tornado Cash in patterns resembling North Korean hacker operations.
The attackers systematically drained funds from SBI Crypto's hot wallets across five blockchains simultaneously, suggesting either extensive reconnaissance or insider knowledge of the wallet infrastructure. The largest portion ($17.45 million) was stolen from Bitcoin wallets, with $6.4 million from Ethereum, and smaller amounts from Bitcoin Cash ($67,874), Litecoin ($76,343), and Dogecoin ($42,718). The Ethereum funds were laundered through multiple routes including 924 ETH to Tornado Cash across 15 transactions, with some funds audaciously cycled back through SBI's own infrastructure before routing to OpenOcean DEX. Bitcoin funds (143.2 BTC) remained largely stationary as of the report date. The attack method remains unexplained by SBI, with possibilities including compromised private keys or supply chain attacks on infrastructure. SBI Holdings issued a vague statement on October 2nd confirming an "unauthorized outflow" while conducting investigations, notably occurring just six months after SBI absorbed DMM Bitcoin customers following their $308 million North Korean hack.
Ethereum Attacker Address:
Bitcoin Attacker Address:
bc1qx0a2kfjd7eweczv8xqjm6rggm40v0nkhfss78l
Bitcoin Cash Attacker Address:
qpv9nh5ktagsmtkqle8z2w4dd3mksskpmy499z7c9k
Litecoin Attacker Address:
ltc1qjyrn9p803efj3p8a0g3fmlevs45kq704ns363t
Dogecoin Attacker Address:
DRiEQuJ9pt3GgNraQmHVTjNg4B7uv1XuGb
Incident Report
Protocol Information
Market Context at Time of Hack
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to SBI Crypto, these are the critical security checks that could have prevented this incident (September 2025).
- Verify all logic paths related to 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 TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
- 01
-
02
Web Archive https://x.com/SBICrypto
- 03
-
04
Reference https://rekt.news/sbi-crypto-rekt
Learn to Prevent the Next SBI Crypto
The SBI Crypto 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.