Incident Overview
FinNexus platform was compromised by malware, leading to the minting and selling of over 323,000,000 FNX tokens by an unknown hacker.
The attacker infiltrated the FinNexus system and managed to recover the private key to the ownership of the FNX token contract. They then transferred the ownership of the contract and proceeded to mint over 323,000,000 FNX. In less than an hour, the hacker sold the minted tokens on both centralized and decentralized exchanges, causing a significant price dump.
Ownership transferred:
https://etherscan.io/tx/0x61f5518e…e38ed0
Mint transaction:
https://etherscan.io/tx/0x15d5debe…a21bbf
Incident Report
Protocol Information
Market Context at Time of Hack
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to FinNexus, these are the critical security checks that could have prevented this incident (May 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 TrialSecurity Audit History
- Audit Report 1 Report
Related Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
Learn to Prevent the Next FinNexus
The FinNexus 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.