Digital Asset
Intelligence
Security Incident · Wallet

Ionic Social Engineering: $12.30M Reported Loss

·Historical incident record

Incident Overview

On February 4, 2025, the Ionic protocol suffered a social engineering attack, allowing the attacker to use a forged Lombard Bitcoin Token (LBTC) as collateral. This asset was deployed on the Mode network. The attacker deployed the forged LBTC on January 9, 2025, while Ionic records indicate that the attacker began interacting with the platform as early as December 12, 2024. After several weeks of business development (BD) discussions, the Ionic team approved the fraudulent asset as eligible collateral and provided a Balancer pool with $400,000 in liquidity, along with API3 oracle price feeds. Ultimately, the Ionic Mode main market accepted the forged LBTC as collateral, with a total supply of 250 LBTC. The attacker minted 250 LBTC in their own wallet and deposited them into Ionic as collateral, stealing $12.3 million worth of supplied assets.

Sources & References

This record presents information attributed to the linked sources. Incident dates describe the original event, not a new report. Reported loss figures reflect the source record and are not current market valuations.

More Security Incidents

View All →
  1. Incident date
    Attack methodAccount Compromise
    Reported lossNot disclosed
  2. Incident date
    Target

    Infini

    Attack methodLack of Strict Access Control
    Reported loss$ 50,000,000
  3. Incident date
    Target

    Suji Yan

    Attack methodUnknown
    Reported loss$ 4,000,000
  4. Incident date
    Attack methodAccount Compromise
    Reported lossNot disclosed
  5. Incident date
    Attack methodAccount Compromise
    Reported lossNot disclosed