Seedify Hack
Incident Overview
On September 23, 2025, Seedify's SFUND token was exploited by DPRK-linked hackers who compromised a developer's private key to mint unauthorized tokens through the cross-chain bridge. The attack resulted in over $1.2 million in losses and caused SFUND to crash 99% from $0.43 to near zero, affecting 64,000 holders across multiple blockchains.
At approximately 12:05 UTC, North Korea state-affiliated hackers gained access to a Seedify developer's private key and exploited the OFT (Omnichain Fungible Token) bridge contract to mint unauthorized SFUND tokens on Avalanche. The attackers modified contract settings to enable unlimited minting, then bridged the tokens cross-chain to Ethereum, Arbitrum, and Base networks where they drained available liquidity pools. The majority of stolen funds were ultimately transferred to BNB Chain and sold before Seedify could contain the breach.
The primary attacker address received over $1.2 million worth of SFUND tokens and began laundering proceeds across multiple wallets. Seedify responded by coordinating with centralized exchanges to halt trading, blacklisting attacker addresses across all affected chains, revoking compromised permissions, and temporarily disabling all cross-chain bridge functionality.
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 Seedify, these are the critical security checks that could have prevented this incident (September 2025).
- Verify all logic paths related to Infinite Mint and Dump / 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
- 01
- 02
- 03
- 04
- 05
Learn to Prevent the Next Seedify
The Seedify 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.