How much was lost in the Bloody Finance hack?

The Bloody Finance hack resulted in $1K in losses on November 05, 2020.

What attack technique was used in the Bloody Finance exploit?

The Bloody Finance exploit utilized Rugpull. Understanding this attack vector is critical for smart contract auditors and developers building secure DeFi protocols.

How can developers prevent similar smart contract attacks?

Preventing smart contract hacks requires a combination of secure coding practices, thorough security audits, and understanding common attack vectors like reentrancy, oracle manipulation, and access control flaws. Smart Contract Hacking (SCH) provides hands-on training to help developers and auditors identify and prevent vulnerabilities before deployment.

Bloody Finance Hack

TOTAL LOST $1K

Low Nov 05, 2020 Rugpull ethereum

Affected Chain ethereum Incident surface

Recovered - No recovery reported

All-Time Rank #2013 By amount stolen

Protocol Type Lending Target category

Incident Overview

The contract deployer added initial liquidity at:

https://etherscan.io/tx/0xf0c3c266…b39693

The contract deployer used hidden minting functionality under the delegateFromAndCall() function to generate new tokens onto his wallet:

https://etherscan.io/tx/0x71dd67aa…ea3e5a

The minted tokens were sold by the contract deployer at:

https://etherscan.io/tx/0x87aa46dc…7f0540

Incident Report

Protocol / Project Bloody Finance

Date of Incident November 05, 2020

Affected Chain(s) ethereum

Attack Technique Rugpull

Classification Token

Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending

Affected Token BLD

Official Website bloody.finance/

Protocol Twitter/X @BflyFinance

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 Bloody Finance's contract logic - root cause: token

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

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

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

Sources & References

01
Source 1 https://twitter.com/0xdeadf4ce/status/1324492128169451521
02
Web Archive https://web.archive.org/web/20201105232033/https://bloody.finance/

Threat Assessment

Severity Level

LOW

Attack Vector Rugpull
Root Cause Token
Year 2020

Learn to Prevent the Next Bloody Finance

The Bloody Finance 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