On January 2025, Paribus was exploited in a other on Arbitrum, resulting in approximately $86K in losses. That makes the Paribus exploit the 231st largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Paribus Other Played Out
Exploit Class Applied to Paribus
The Paribus incident on January 18, 2025 is classified as a Other. A specific exploit class outside the most common buckets. In the full archive, Paribus is 1 of 188 documented other incidents.
Paribus in Context
At $86K, the Paribus exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — MIMSpell (2024) at $65M.
Prior Other Before Paribus
The nearest other incident before Paribus was LPMine, 10 days earlier on January 8, 2025 ($24K lost). The same exploit class surfaced again within the other attack surface.
Paribus Vulnerability Signature
The primary source categorises the Paribus exploit specifically as “Bad oracle”. This narrower label is entity-specific: it reflects how the Paribus contract failed, rather than the broad other pattern alone.
Target Chain: Arbitrum
The vulnerable Paribus contract was deployed on Arbitrum. This determines the block cadence, mempool, and forensic tooling available to investigators.
Impact & Recovery for Paribus
Paribus Loss Figure
The Paribus exploit caused $86,000 in losses — a minor (<$1M) incident and the 32nd largest of 96 documented in 2025.
Where Paribus Sits Among Other Attacks
Ranked by loss size, Paribus is the 51st largest of 188 other incidents documented. That puts the Paribus loss below the class average of $2.03M.
Timeline Since the Paribus Incident
The Paribus exploit occurred 1.2 years ago (451 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for Paribus
Public post-mortem / on-chain analysis for the Paribus incident: view source.
FAQ
How much did Paribus lose?
The Paribus exploit in January 2025 resulted in $86,000 in losses — the 32nd largest of 96 DeFi incidents that year.
When did the Paribus hack happen?
The Paribus exploit was recorded on January 18, 2025 — 451 days ago.
What type of exploit hit Paribus?
The Paribus incident is classified as a Other. A specific exploit class outside the most common buckets.
Which blockchain was Paribus deployed on?
The Paribus contract was deployed on Arbitrum, one of 1 documented incidents on that chain.
How does Paribus compare to the largest Other attack?
The largest other incident in our archive is MIMSpell (2024) at $65M. The Paribus loss is $86K.
What is a key development in the rise of cryptocurrencies?
The emergence of cryptoexchanges, where cryptoassets are traded, is a key development.
What does the experimental evaluation of the BBDSPP scheme reveal about its performance?
The evaluation shows the scheme is efficient in terms of computational and storage resources, making it suitable for IIoT applications.