← Ionic Moneyreviewed 2026-09-06 · 26 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Ionic Money against the sources the page cites. Only the most recent review is shown.
Read this first
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
3 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #13[disputed][awaiting moderator]in section: Predecessor Protocol Midas Capital — Two Prior Exploits (2023)
“The first exploit occurred on January 16, 2023, when an attacker used a flash loan to exploit a read-only reentrancy vulnerability in the WMATIC-stMATIC Curve LP token collateral on Midas's Jarvis Polygon pool, resulting in approximately $660,000 in losses.”
reviewerThe first Midas Capital exploit occurred on January 16, 2023 (Jarvis Polygon pool, WMATIC-stMATIC read-only reentrancy, ~$660,000 lost).Multiple independent sources (Rekt News, PeckShield's original alert, contemporaneous news coverage) converge on January 15, 2023, not January 16, 2023, for this exploit. The $660,000 figure and technical description are otherwise accurate.Proposed correction (not yet applied)The first exploit occurred on January 15, 2023, when an attacker used a flash loan to exploit a read-only reentrancy vulnerability in the WMATIC-stMATIC Curve LP token collateral on Midas's Jarvis Polygon pool, resulting in approximately $660,000 in losses. - #20[disputed][awaiting moderator]in section: Current Status and TVL
“DeFi Llama data available in mid-2025 reflects a TVL of approximately $2 million, substantially below earlier reported figures of over $250 million that the protocol cited across its multi-chain deployments on Mode Network, Base, Optimism, and BOB.”
reviewerMid-2025 TVL was approximately $2 million, down from earlier reported figures of over $250 million across Mode, Base, Optimism, and BOB.The $2 million mid-2025 figure is precisely confirmed by DeFiLlama's own API data. However, the peak TVL never reached 'over $250 million' -- the actual all-time high per DeFiLlama was approximately $244.85 million, which is under, not over, $250M.Proposed correction (not yet applied)DeFi Llama data available in mid-2025 reflects a TVL of approximately $2 million, substantially below earlier reported figures of approximately $245 million that the protocol cited across its multi-chain deployments on Mode Network, Base, Optimism, and BOB. - #24[disputed][awaiting moderator]in the timeline
“2023-01-16”
reviewerThe Midas Capital Jarvis Polygon pool exploit is dated 2023-01-16 in the timeline.Same underlying date error as the corresponding section[3] narrative claim; both should be corrected together.Proposed correction (not yet applied)2023-01-15
unverifiable
3 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #6[unverifiable][awaiting moderator]in section: February 2025 Social Engineering Exploit (~$8.6–8.8M)
“Attackers impersonated members of the Lombard Finance team over an extended business development process beginning as early as December 2024.”
reviewerAttackers impersonated Lombard Finance team members over an extended business development process beginning as early as December 2024.General secondary reporting confirms a multi-week impersonation campaign preceding the January 2025 contract deployment, consistent with a December 2024 start, but the specific date could not be independently verified because the cited Halborn post was rate-limiting all fetch attempts. - #11[unverifiable][awaiting moderator]in section: February 2025 Social Engineering Exploit (~$8.6–8.8M)
“The Ionic team characterized the incident as 'not a code-based breach' and stated their smart contract protocol functioned as intended; they advised users to suspend platform interaction while the investigation proceeded and stated they were engaging law enforcement and investigative partners.”
reviewerIonic characterized the incident as 'not a code-based breach,' advised suspending platform interaction, and stated they were engaging law enforcement.The general narrative (social engineering, not a code exploit, team response) is consistent with secondary reporting, but the specific quoted phrasing and the claim that law enforcement was engaged could not be independently verified because the primary cited source was inaccessible. - #25[unverifiable][awaiting moderator]in the timeline
“Alleged attacker begins interacting with Ionic Money platform, initiating multi-week impersonation of Lombard Finance team members.”
reviewerThe attacker began interacting with the Ionic platform, initiating impersonation of Lombard Finance, on 2024-12-12.The general timeframe (weeks of engagement before the January 2025 contract deployment) is plausible and consistent with secondary reporting, but the exact day-level date is unverifiable given inability to access the primary cited source.
stale
1 claimThe claim was accurate when written but events since have overtaken it.
- #22[stale][awaiting moderator]in section: Current Status and TVL
“The protocol's operational status and whether it remains actively maintained is not clearly established in publicly available sources.”
reviewerThe protocol's operational status and whether it remains actively maintained is not clearly established in publicly available sources.This claim was accurate at the time the page was researched but has since been superseded: Ionic announced a permanent shutdown around June 2026, corroborated by multiple independent reports. This is the single most significant update the page is missing.Proposed correction (not yet applied)The protocol permanently shut down in June 2026, with the team citing the lasting financial and reputational damage from the February 2025 exploit; no compensation plan for affected users was announced.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in the summary
“In February 2025, Ionic Money suffered a social engineering attack in which attackers impersonating the Lombard Finance team convinced the protocol to list a counterfeit LBTC token as collateral, resulting in approximately $8.6–8.8 million in losses.”
reviewerIn Feb 2025, attackers impersonating Lombard Finance convinced Ionic to list counterfeit LBTC, resulting in approximately $8.6-8.8 million in losses.The $8.6-8.8M range is the majority figure (Halborn, PANews, QuillAudits, DeFiLlama's $8.6M), but Rekt News -- cited by the page as a source for this exact figure -- reports $6.9M total loss. The page presents a single range without noting this disagreement among its own cited sources.
confirmed
18 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“Ionic Money is a decentralized money market protocol operating on Mode Network (an OP Superchain L2), rebranded from Midas Capital after two exploits on that predecessor protocol in 2023.”
reviewerIonic Money is a decentralized money market protocol on Mode Network (OP Superchain L2), rebranded from Midas Capital after two 2023 exploits.Core identity claim is well corroborated by DeFiLlama chain data and the official Ionic introduction post. - #3[confirmed][no action needed]in the summary
“The protocol and its affiliated ecosystem protocols on Mode Network absorbed significant bad debt, with no confirmed user compensation as of mid-2025.”
reviewerIonic and affiliated Mode ecosystem protocols absorbed bad debt with no confirmed user compensation as of mid-2025.Accurate as a time-bound statement; later reporting confirms no compensation plan was ever announced even through the protocol's eventual shutdown. - #4[confirmed][no action needed]in section: Protocol Overview
“Ionic was developed by a team with overlapping leadership from Midas Capital, an earlier multi-chain lending protocol that operated on BNB Chain and Polygon. The team sunsetted Midas in favor of a 'Superchains first' strategy, focusing development resources on the Mode Network ecosystem.”
reviewerIonic was developed by a team with overlapping leadership from Midas Capital (BNB Chain/Polygon lending protocol), sunsetted in favor of a 'Superchains first' strategy.Verbatim-consistent with the official introduction post. - #5[confirmed][no action needed]in section: Protocol Overview
“Ionic received seed investment from MetaCartel Ventures and grants from projects including Neon, OHM, and Kaizen DAO.”
reviewerIonic received seed investment from MetaCartel Ventures and grants from Neon, OHM, and Kaizen DAO.Directly confirmed by the cited primary source. - #7[confirmed][no action needed]in section: February 2025 Social Engineering Exploit (~$8.6–8.8M)
“By January 9, 2025, the attackers had deployed a counterfeit LBTC token contract (0x964dd444e3192f636322229080a576077b06fba3).”
reviewerBy January 9, 2025, attackers had deployed a counterfeit LBTC token contract at 0x964dd444e3192f636322229080a576077b06fba3.Contract address verified against an independent case study; January 2025 deployment timing consistent across multiple secondary sources. - #8[confirmed][no action needed]in section: February 2025 Social Engineering Exploit (~$8.6–8.8M)
“Once listed, the attackers minted 250 counterfeit LBTC tokens and used them to borrow multiple real assets from the protocol, including MBTC, uniBTC, wrsETH, WETH, and STONE.”
reviewerAttackers minted 250 counterfeit LBTC and used them to borrow MBTC, uniBTC, wrsETH, WETH, and STONE.Directly confirmed by Rekt News and Quadriga Initiative. - #9[confirmed][no action needed]in section: February 2025 Social Engineering Exploit (~$8.6–8.8M)
“Approximately 1,204 ETH (valued at roughly $3.2 million at the time) was bridged to Ethereum and laundered through Tornado Cash.”
reviewerApproximately 1,204 ETH (~$3.2 million) was bridged to Ethereum and laundered through Tornado Cash.Precisely corroborated by the cited source. - #10[confirmed][no action needed]in section: February 2025 Social Engineering Exploit (~$8.6–8.8M)
“An additional approximately $3.7 million in MBTC loans remained on Mode Network.”
reviewerAn additional approximately $3.7 million in MBTC loans remained on Mode Network.Matches cited source figure exactly. - #12[confirmed][no action needed]in section: Ecosystem Contagion from 2025 Exploit
“In particular, Layerbank and Ironclad — two other lending protocols in the Mode ecosystem — were left holding toxic MBTC positions that became effectively worthless after the snapshot action.”
reviewerLayerbank and Ironclad were left holding toxic MBTC positions after Merlin Chain's snapshot action.Directly corroborated, near-verbatim, by the cited source. - #14[confirmed][no action needed]in section: Predecessor Protocol Midas Capital — Two Prior Exploits (2023)
“The second exploit occurred on June 17, 2023, on BNB Chain, resulting in approximately $600,000 in losses via a rounding error vulnerability in the protocol's Compound V2 fork codebase; the attacker used flash loans to exploit the rounding issue in voucher value calculations.”
reviewerThe second Midas Capital exploit occurred on June 17, 2023, on BNB Chain via a rounding error in the Compound V2 fork codebase, ~$600,000 lost.Date, chain, mechanism, and loss figure all confirmed by an independent technical write-up. - #15[confirmed][no action needed]in section: Predecessor Protocol Midas Capital — Two Prior Exploits (2023)
“On-chain investigator ZachXBT stated publicly in February 2025 that he had privately confronted the Ionic team about these prior Midas exploits before the February 2025 incident, and that Ionic had launched using an audit report from Midas dated 2022.”
reviewerZachXBT stated in February 2025 that he had privately confronted the Ionic team about the prior Midas exploits and that Ionic launched using a 2022 Midas audit report.Corroborated via independent secondary reporting on ZachXBT's statement; the tweet itself could not be fetched directly (403) but its substance is echoed consistently elsewhere. - #16[confirmed][no action needed]in section: Collateral Vetting and Operational Risk
“The attack succeeded not through a smart contract vulnerability but through manipulation of the protocol's off-chain due diligence and governance processes.”
reviewerThe exploit succeeded through manipulation of off-chain due diligence and governance processes rather than a smart contract vulnerability.Consistent across all sources reviewed; uncontested characterization of the exploit. - #17[confirmed][no action needed]in section: ezETH Integration and April 2024 Depeg Context
“In March 2024, Ionic Money announced that Renzo Protocol's ezETH (a liquid restaking token) would be the first LRT integrated as collateral on the protocol via a RedStone oracle price feed.”
reviewerIn March 2024, Ionic Money announced Renzo Protocol's ezETH as the first LRT collateral via a RedStone oracle price feed.Independently verified via Snowflake ID timestamp decoding, which confirmed the exact tweet date used in the timeline. - #18[confirmed][no action needed]in section: ezETH Integration and April 2024 Depeg Context
“In late April 2024, ezETH experienced a significant depeg event following Renzo Protocol's controversial REZ tokenomics announcement, with ezETH briefly trading as low as approximately $688 on Uniswap — an 18% discount to ETH. This depeg triggered over $60 million in liquidations across DeFi platforms that accepted ezETH as collateral, particularly Morpho and Gearbox.”
reviewerIn late April 2024, ezETH depegged to ~$688 on Uniswap (~18% discount to ETH), triggering over $60 million in DeFi liquidations concentrated at Morpho and Gearbox.Price, percentage, exchange, cause, total liquidation figure, and affected platforms all independently corroborated. - #19[confirmed][no action needed]in section: Team Anonymity and Governance
“The project's introductory publication references 'a handful of ambitious giga brains' initiating the protocol in November 2021 under the Midas Capital name, without naming individuals.”
reviewerThe Ionic team has not disclosed founder identities; the introductory post refers only to 'a handful of ambitious giga brains' founding the protocol in November 2021.Verbatim match to the official source; no named individuals found in any official Ionic material reviewed. - #21[confirmed][no action needed]in section: Current Status and TVL
“As of mid-2025, no confirmed compensation plan for users who suffered losses in the February 2025 exploit has been publicly announced.”
reviewerAs of mid-2025, no confirmed compensation plan for users affected by the February 2025 exploit had been publicly announced.Consistent with the eventual outcome; no compensation plan was ever announced through the protocol's later shutdown. - #23[confirmed][no action needed]in the timeline
“Midas Capital protocol initiated by anonymous team on Polygon and BNB Chain as a multi-chain isolated lending market.”
reviewerMidas Capital protocol was initiated by an anonymous team on Polygon and BNB Chain in November 2021.Date and description match the official source. - #26[confirmed][no action needed]in the timeline
“Ionic Money exploit executed: 250 counterfeit LBTC tokens used as collateral to borrow approximately $8.6–8.8M in real assets including MBTC, uniBTC, wrsETH, WETH, and STONE. Approximately 1,204 ETH bridged to Ethereum and routed through Tornado Cash.”
reviewerThe Ionic Money exploit was executed on 2025-02-04, involving the counterfeit LBTC collateral scheme and Tornado Cash laundering.The February 4, 2025 date is independently corroborated by DeFiLlama's structured hacks dataset, separate from the page's narrative sources.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.