Rubic Hack

TOTAL LOST $80K
Low Access Control

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #1593 By amount stolen
Auditors 2 Prior security audits

Incident Overview

Rubic platform was exploited for 79,670 $USD. The attacker compromised private keys and transferred funds to an EOA address.

Rubic is a DEX aggregator and multichain bridge. The project's wallet on the Binance Chain was exploited via access control. The attacker took 79,670 $USD worth of assets including $BRBC, $BNB, and several stablecoins.

All the stolen funds remain on the attacker's EOA address.

Attacker address:

https://bscscan.com/address/0xd2d113d7…25f24a

Incident Report

Protocol / Project Rubic
Date of Incident
Attack Technique Access Control
Classification Bridge,Exchange (DEX)
Primary Source View Post-Mortem

Protocol Information

Protocol Type DEX Aggregator
Affected Token BRBC
Official Website rubic.exchange/
Protocol Twitter/X @CryptoRubic
Team Public / Doxxed
Source Code Unverified

Market Context at Time of Hack

Token Categories
DeFi Ethereum Ecosystem Arbitrum Ecosystem BNB Chain Ecosystem

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 Rubic'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 Access Control audit checklist and test coverage
Audited by Audit Report 1, Audit Report 2 — still lost $80K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • 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 Trial

Security Audit History

Related Attack Classes

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

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next Rubic

The Rubic 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.

Recreate exploit patterns safely Free Trial