Seedify’s SFUND implodes 99%, DPRK hackers exploit bridge flaw
The post Seedify’s SFUND implodes 99%, DPRK hackers exploit bridge flaw appeared on BitcoinEthereumNews.com. Seedify’s SFUND token was virtually erased in minutes, collapsing from $0.43 to near zero. The plunge follows a confirmed exploit on a cross-chain bridge, sparking an investigation and a direct plea to Binance’s Changpeng Zhao for help. Summary Seedify’s SFUND token collapsed nearly 100% after a cross-chain bridge exploit allowed attackers to mint and dump massive amounts of tokens. The plummet affected 64,000 holders and $1.2 million in assets. The team has since halted trading, blacklisted malicious addresses, and temporarily disabled all bridges, while appealing for outside help to track the perpetrators and recover stolen funds. On Sept. 23, Seedify’s SFUND token suffered one of the sharpest collapses seen in recent memory, plunging 99.99% from $0.43 to nearly worthless within minutes before stabilizing above $0.21 at the time of writing, according to CoinMarketCap data. The crash followed confirmation from founder Levent Cem Aydan that the project’s cross-chain bridge had been compromised, allowing attackers to mint and dump vast amounts of SFUND across multiple blockchains. Source: CoinGecko In a public plea posted to X, Aydan appealed directly to Binance founder Changpeng Zhao for help, citing more than $1.2 million in stolen assets tied to 64,000 affected holders on BNB Chain. Hi @cz_binance a few hours ago our bridge/oft contract got hacked, and hackers transferred minted tokens onto many chains, including BNB, where they sold most of the $SFUND tokens. Currently they hold more than $1.2M in BNBchain:0x14181636dd5BC8C6b8b47F8D0fd1b1e351B84bE4 A lot… — Meta Alchemist (@meta_alchemist) September 23, 2025 Seedify’s response and what the exploit revealed Roughly three hours after Aydan’s first acknowledgment of the breach, Seedify’s official X account issued a detailed statement. The team attributed the exploit to a DPRK state-affiliated group, saying the attackers gained control of a developer’s private keys. According to the announcement, the breach occurred at approximately 12:05…
The post Seedify’s SFUND implodes 99%, DPRK hackers exploit bridge flaw appeared on BitcoinEthereumNews.com.
Seedify’s SFUND token was virtually erased in minutes, collapsing from $0.43 to near zero. The plunge follows a confirmed exploit on a cross-chain bridge, sparking an investigation and a direct plea to Binance’s Changpeng Zhao for help. Summary Seedify’s SFUND token collapsed nearly 100% after a cross-chain bridge exploit allowed attackers to mint and dump massive amounts of tokens. The plummet affected 64,000 holders and $1.2 million in assets. The team has since halted trading, blacklisted malicious addresses, and temporarily disabled all bridges, while appealing for outside help to track the perpetrators and recover stolen funds. On Sept. 23, Seedify’s SFUND token suffered one of the sharpest collapses seen in recent memory, plunging 99.99% from $0.43 to nearly worthless within minutes before stabilizing above $0.21 at the time of writing, according to CoinMarketCap data. The crash followed confirmation from founder Levent Cem Aydan that the project’s cross-chain bridge had been compromised, allowing attackers to mint and dump vast amounts of SFUND across multiple blockchains. Source: CoinGecko In a public plea posted to X, Aydan appealed directly to Binance founder Changpeng Zhao for help, citing more than $1.2 million in stolen assets tied to 64,000 affected holders on BNB Chain. Hi @cz_binance a few hours ago our bridge/oft contract got hacked, and hackers transferred minted tokens onto many chains, including BNB, where they sold most of the $SFUND tokens. Currently they hold more than $1.2M in BNBchain:0x14181636dd5BC8C6b8b47F8D0fd1b1e351B84bE4 A lot… — Meta Alchemist (@meta_alchemist) September 23, 2025 Seedify’s response and what the exploit revealed Roughly three hours after Aydan’s first acknowledgment of the breach, Seedify’s official X account issued a detailed statement. The team attributed the exploit to a DPRK state-affiliated group, saying the attackers gained control of a developer’s private keys. According to the announcement, the breach occurred at approximately 12:05…
What's Your Reaction?
