GAIN May Have Suffered Unauthorized 5B Mint on BNB Chain After Alleged Fake LayerZero Peer, Prompting Liquidity Removal

• Attacker minted 5,000,000,000 GAIN via a fake LayerZero peer and dumped 147.5M tokens for ~2,955 BNB.

• Griffin AI removed official BNB Chain liquidity and warned users not to interact with attacker-created pools.

• Project contacted exchanges to suspend GAIN (BSC) trading, deposits, and withdrawals while coordinating containment.

Griffin AI exploit: GAIN token minted 5B on BNB Chain, dumped for ~2,955 BNB — check security updates and avoid attacker pools. Read the full incident report.

What happened in the Griffin AI exploit on BNB Chain?

Griffin AI exploit occurred when a malicious fake LayerZero peer replaced the official Ethereum endpoint peer, enabling an attacker to mint 5 billion GAIN on BNB Chain and rapidly dump 147.5 million tokens for about 2,955 BNB. The team removed BSC liquidity and is coordinating with exchanges and security partners.

How did the attacker mint 5 billion GAIN tokens?

On-chain records show address 0xF3…8Db2 minted 5,000,000,000 GAIN from a null address at 07:04 (UTC+8), raising total supply to 5.2985B. Investigators traced the minting vector to a fake Ethereum contract (0x7a8caf) inserted as a LayerZero peer, overriding the official peer at 0xccdbb9 and allowing unauthorized mints on BNB Chain.

Who confirmed the breach and what did they say?

Founder & CEO Oliver Feldmeier confirmed the events via the project’s official social channel (X). He stated the fake LayerZero peer enabled abnormal minting and dumping, that the Ethereum deployment remains unaffected, and that the team is working with exchanges and security partners to contain the impact.

Why did the GAIN token price crash over 90%?

The sudden supply inflation — a 5B unauthorized mint — and immediate dumping of newly minted GAIN into PancakeSwap liquidity pools caused market depth to collapse and triggered a >90% price decline. Rapid selling pressure and removed official liquidity amplified the downward move.

What on-chain evidence supports the timeline?

Chain activity shows 0xF3…8Db2 minted 5B GAIN, then sold 147.5M GAIN on PancakeSwap, receiving at least 2,955 BNB. Funds were subsequently bridged using deBridge. These transactions are observable in public chain data and were cited by Griffin AI in their incident updates.

How is Griffin AI responding to the exploit?

Griffin AI removed official liquidity on BNB Chain and publicly warned users not to interact with pools that could be attacker-created. The team has asked centralized exchanges to suspend GAIN (BSC) trading, deposits, and withdrawals while security coordination and investigations continue.

What immediate security actions are recommended?

• Do not trade or provide liquidity for GAIN on BSC until official updates are posted.
• Monitor official Griffin AI communications and on-chain explorer data for wallet movement.
• Exchanges and custodians should freeze affected markets and trace bridged funds.

Frequently Asked Questions

How can I check if my tokens are safe after the exploit?

Check whether you hold GAIN on BNB Chain and avoid any BSC pools referencing GAIN. Verify balances via on-chain explorers and follow Griffin AI official updates for wallet or contract advisories.

What should exchanges do to limit damage?

Exchanges should suspend GAIN (BSC) trading, deposits, and withdrawals, freeze suspicious wallets if possible, and coordinate with Griffin AI and blockchain security firms to trace bridged funds.

Key Takeaways

• Root cause: Fake LayerZero peer replaced the official Ethereum endpoint, enabling unauthorized mints.
• Impact: 5B GAIN minted, 147.5M dumped for ~2,955 BNB, >90% price crash on BSC.
• Action: Avoid BSC GAIN pools, follow official Griffin AI updates, and await exchange containment measures.

Conclusion

The Griffin AI exploit exposed a LayerZero integration vulnerability that allowed mass minting and rapid dumping of GAIN on BNB Chain. Griffin AI removed BSC liquidity and requested exchange suspensions while security partners investigate. Token holders should avoid BSC interactions and monitor official updates as remediation and tracing continue.