8ight Finance Hack

TOTAL LOST $924K
Low Access Control

Summarize with AI

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

Incident Overview

The project's team stated: "Our private key got compromised and the funds have been transferred out of the treasury."

As a result, the address that received access control withdrew:

- 490,170 DAI

https://explorer.harmony.one/tx/0x7a9aeca3…9af964

- 378,417 DAI - 10,843 LP

https://explorer.harmony.one/tx/0x0af0e8ea…dc70b2

- 12,362 USDT

https://explorer.harmony.one/tx/0x71a8fa40…ec5bf9

Transfer from xxca1d account to cc541:

https://explorer.harmony.one/tx/0xbe7617d4…797bec

Funds were delivered into Ethereum and deposited into Tornado Cash mixer:

https://etherscan.io/address/0x4d807145…04ca1d

Incident Report

Protocol / Project 8ight Finance
Date of Incident
Attack Technique Access Control
Classification Other

Protocol Information

Protocol Type Yield Aggregator
Official Website 8ight.finance/
Protocol Twitter/X @8ight_finance
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Memes 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 8ight Finance'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 β€” still lost $924K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • 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 8ight Finance

The 8ight 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.

Recreate exploit patterns safely Free Trial