On January 2025, Mosca was exploited in a business logic flaw, resulting in approximately $19K in losses. That makes the Mosca exploit the 336th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Mosca Business Logic Flaw Played Out
Exploit Class Applied to Mosca
The Mosca incident on January 6, 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, Mosca is 1 of 144 documented business logic flaw incidents.
Mosca in Context
At $19K, the Mosca 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 Mosca
The nearest business logic flaw incident before Mosca was SlurpyCoin, 19 days earlier on December 18, 2024 ($3K lost). The same exploit class surfaced again within the business logic flaw attack surface.
Mosca Vulnerability Signature
The primary source categorises the Mosca exploit specifically as “Logic Flaw”. This narrower label is entity-specific: it reflects how the Mosca contract failed, rather than the broad business logic flaw pattern alone.
Impact & Recovery for Mosca
Mosca Loss Figure
The Mosca exploit caused $19,000 in losses — a minor (<$1M) incident and the 57th largest of 96 documented in 2025.
Where Mosca Sits Among Business Logic Flaw Attacks
Ranked by loss size, Mosca is the 70th largest of 144 business logic flaw incidents documented. That puts the Mosca loss below the class average of $6.08M.
Timeline Since the Mosca Incident
The Mosca exploit occurred 1.3 years ago (463 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
FAQ
How much did Mosca lose?
The Mosca exploit in January 2025 resulted in $19,000 in losses — the 57th largest of 96 DeFi incidents that year.
When did the Mosca hack happen?
The Mosca exploit was recorded on January 6, 2025 — 463 days ago.
What type of exploit hit Mosca?
The Mosca 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 Mosca?
Our archive contains 144 documented business logic flaw incidents. The Mosca incident is one of them.
How does Mosca compare to the largest Business Logic Flaw attack?
The largest business logic flaw incident in our archive is – EulerFinance (2023) at $200M. The Mosca loss is $19K.
What is the primary reason companies seek to implement blockchain in supply chains?
To increase operational transparency and efficiency in the supply chain.
What percentage of disaster response costs is accounted for by logistics management?
About 80% of the total costs related to disaster response.