Bacon Protocol Hack

TOTAL LOST $957K
Low Flash Loan Attack

Summarize with AI

Affected Chain 2022 Incident surface
Recovered $957K 100.0% returned
All-Time Rank #850 By amount stolen
Protocol Type Services Target category

Incident Overview

The exploiter's address:

https://etherscan.io/address/0x7c42f2a7…607593

The transaction behind the exploit:

https://etherscan.io/tx/0x7d2296bc…dbcf31

The hack is made possible due to a reentrancy bug in the lend() routine so that the exploiter can get more lending credits via re-entering the lend() routine.

The contract exploit led to sending 957,166 USDC out of the protocol. A second exploit was prevented by a white hat group who returned the 34,232 USDC they received. These changes caused the price of bHOME to temporarily unpeg and decrease to $0.86.

As of March 6th, the BaconCoin team has deposited 991,441 USDC into the BaconCoin multi-sig that will be used to recapitalize the protocol:

https://etherscan.io/tx/0xf13823ec…bdcdc7

https://etherscan.io/tx/0x23ccdd96…8dc668

Incident Report

Protocol / Project Bacon Protocol
Date of Incident
Attack Technique Flash Loan Attack
Classification Other

Protocol Information

Protocol Type Services
Affected Token bHOME
Official Website www.baconcoin.com/
Protocol Twitter/X @BaconProtocol
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Marketplace Collectibles & NFTs E-commerce Gaming Payments Ethereum Ecosystem Metaverse Exnetwork Capital Portfolio

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 flash loan attack and Solidity and EVM internals
Capital Required Flash loan capital (borrowed atomically, zero upfront cost)
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Bacon Protocol's contract logic - root cause: other
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? Yes — skilled auditors routinely flag Flash Loan Attack vulnerabilities in code review

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

  • Verify all logic paths related to Flash Loan Attack are guarded by proper access controls and input validation - see the Flash Loans 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

Funds Recovery

100.0%

Recovered

$957K

Net Loss

0

Related Attack Classes

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

See all Flash Loans Attacks examples →

Sources & References

Learn to Prevent the Next Bacon Protocol

The Bacon 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