Seedify Hack

TOTAL LOST $1.2M
Medium Infinite Mint and Dump / Access Control avalanche bsc

Summarize with AI

Affected Chain avalanche 2 chains affected
Recovered - No recovery reported
All-Time Rank #774 By amount stolen
Auditors 1 Prior security audit

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.

Primary Attacker Address:

0x14181636…B84bE4

Incident Report

Protocol / Project Seedify
Date of Incident
Affected Chain(s) avalanche bsc
Attack Technique Infinite Mint and Dump / Access Control
Classification Infrastructure / Bridge
Primary Source View Post-Mortem

Protocol Information

Protocol Type Launchpad
Smart Contract Language Solidity
Official Website seedify.fund/
Protocol Twitter/X @seedifyfund
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Price at Hack $0.4257
Market Cap at Hack $27.0M
% of Market Cap Stolen 4.44%
Token Categories
Gaming (GameFi) BNB Chain Ecosystem Launchpad DWF Labs Portfolio

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 Seedify'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 Infinite Mint and Dump / Access Control audit checklist and test coverage
Audited by Audit Report 1 — still lost $1.2M. Prior audits don't guarantee safety, especially after post-audit code changes.

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 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 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.

Recreate exploit patterns safely Free Trial