Binary Protocol Hack

TOTAL LOST $4K
Low Rugpull ethereum

Summarize with AI

Affected Chain ethereum Incident surface
Recovered - No recovery reported
All-Time Rank #1990 By amount stolen
Auditors 1 Prior security audit

Incident Overview

The contract deployer used a hidden minting functionality under the function initialSupply(), which was invoked by the contract deployer 3 times:

https://etherscan.io/tx/0x7467abb5…93a521

https://etherscan.io/tx/0xf4b6c140…c2293c

https://etherscan.io/tx/0x672689de…3dc887

In the function input data, the recipient address of the minted tokens was this address:

0xD97A7501…34050C

This external wallet added initial liquidity at:

https://etherscan.io/tx/0x1cdad510…825da5

The transaction, where the external wallet sold tokens:

https://etherscan.io/tx/0x0c02a010…41b083

Incident Report

Protocol / Project Binary Protocol
Date of Incident
Affected Chain(s) ethereum
Attack Technique Rugpull
Classification Exchange (DEX)
Primary Source View Post-Mortem

Protocol Information

Protocol Type Liquid Staking
Affected Token BP
Official Website linearprotocol.org
Protocol Twitter/X @LinearProtocol

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 Deep understanding of rugpull and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with ethereum smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Binary Protocol's contract logic - root cause: exchange (dex)
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
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? Hard to catch — private key / OpSec failures are outside smart contract audit scope
Audited by Audit Report 1 — still lost $4K. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Binary Protocol, these are the critical security checks that could have prevented this incident (January 2021).

  • Verify all logic paths related to Rugpull are guarded by proper access controls and input validation
  • 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

Sources & References

Learn to Prevent the Next Binary Protocol

The Binary Protocol 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