On January 2025, Mosca2 was exploited in a business logic flaw, resulting in approximately $37.6K in losses. That makes the Mosca2 exploit the 286th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Mosca2 Business Logic Flaw Played Out
Exploit Class Applied to Mosca2
The Mosca2 incident on January 13, 2025 is classified as a Business Logic Flaw. A business-logic bug in the contract — such as an incorrect formula or missing state update — lets the attacker withdraw more than their share. In the full archive, Mosca2 is 1 of 144 documented business logic flaw incidents.
Mosca2 in Context
At $37.6K, the Mosca2 exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — – EulerFinance (2023) at $200M.
Prior Business Logic Flaw Before Mosca2
The nearest business logic flaw incident before Mosca2 was Unilend, 1 day earlier on January 12, 2025. The same exploit class surfaced again within the business logic flaw attack surface.
Mosca2 Vulnerability Signature
The primary source categorises the Mosca2 exploit specifically as “Logic Flaw”. This narrower label is entity-specific: it reflects how the Mosca2 contract failed, rather than the broad business logic flaw pattern alone.
Impact & Recovery for Mosca2
Mosca2 Loss Figure
The Mosca2 exploit caused $37,600 in losses — a minor (<$1M) incident and the 45th largest of 96 documented in 2025.
Where Mosca2 Sits Among Business Logic Flaw Attacks
Ranked by loss size, Mosca2 is the 55th largest of 144 business logic flaw incidents documented. That puts the Mosca2 loss below the class average of $6.08M.
Timeline Since the Mosca2 Incident
The Mosca2 exploit occurred 1.2 years ago (456 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for Mosca2
Public post-mortem / on-chain analysis for the Mosca2 incident: view source.
FAQ
How much did Mosca2 lose?
The Mosca2 exploit in January 2025 resulted in $37,600 in losses — the 45th largest of 96 DeFi incidents that year.
When did the Mosca2 hack happen?
The Mosca2 exploit was recorded on January 13, 2025 — 456 days ago.
What type of exploit hit Mosca2?
The Mosca2 incident is classified as a Business Logic Flaw. A business-logic bug in the contract — such as an incorrect formula or missing state update — lets the attacker withdraw more than their share.
How common is the Business Logic Flaw pattern seen at Mosca2?
Our archive contains 144 documented business logic flaw incidents. The Mosca2 incident is one of them.
How does Mosca2 compare to the largest Business Logic Flaw attack?
The largest business logic flaw incident in our archive is – EulerFinance (2023) at $200M. The Mosca2 loss is $37.6K.
Which cryptocurrencies are analyzed in the document?
Bitcoin, Ether, and XRP are the cryptocurrencies analyzed.
What future research directions does the document suggest?
Further analysis of COVID-19's long-term effects on society and the economy.