Incident Overview
On January 29, 2025, a phishing attack resulted in the loss of 16,939.28 LINK (~$394,000) from the wallet chickengenius.eth. The attacker tricked the victim into signing a malicious transaction, allowing them to drain the funds.
The exploit involved phishing tactics that convinced the victim to approve a transaction granting the attacker access to their LINK tokens. Once approved, the attacker swiftly transferred the stolen assets across multiple addresses: 0x1fd833f5…dec7d7, 0x1fe92e28…724da6, and 0x7d17eff8…a2c95c.
Incident Report
Protocol Information
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 phishing, these are the critical security checks that could have prevented this incident (January 2025).
- Verify all logic paths related to Phishing are guarded by proper access controls and input validation - see the Phishing 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 TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
Learn to Prevent the Next phishing
The phishing 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.