Paribus Hack

TOTAL LOST $70K
Low Reentrancy

Summarize with AI

Affected Chain 2023 Incident surface
Recovered - No recovery reported
All-Time Rank #1638 By amount stolen
Protocol Type Lending Target category

Incident Overview

Paribus was exploited due to a reentrancy issue, resulting in the loss of 69,696 $USD worth of $ETH.

Paribus is a cross-chain lending and borrowing protocol. The protocol suffered an exploit on the Arbitrum layer-two chain. The root cause was a well-known reentrancy vulnerability from an old version of CompoundV2 that Paribus had forked. The attacker deployed two malicious unverified contracts and used this vulnerability to withdraw funds multiple times before updating their balance on-chain. As a result, they were able to drain 35.2 $ETH which is currently worth 69,696 $USD at the time of writing.

All stolen assets were transferred through Stargate Bridge in two transactions.

Attacker address:

https://arbiscan.io/address/0x014abff0…9e5504

Malicious transaction:

https://arbiscan.io/tx/0x0e29dcf4…2390af

Malicious contracts:

https://arbiscan.io/address/0xcd31e27f…f8c50b

https://arbiscan.io/address/0xec05281d…29dfe7

Incident Report

Protocol / Project Paribus
Date of Incident
Attack Technique Reentrancy
Classification Borrowing and Lending
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Affected Token pUSDT
Official Website paribus.io
Protocol Twitter/X @paribus_io
Team Public / Doxxed
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
DeFi Ethereum Ecosystem Lending & Borrowing Cardano Ecosystem Arbitrum Ecosystem

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of reentrancy and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Paribus's contract logic - root cause: borrowing and lending
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Yes — skilled auditors routinely flag Reentrancy vulnerabilities in code review

If you're auditing a protocol with similar architecture to Paribus, these are the critical security checks that could have prevented this incident (April 2023).

  • Verify all logic paths related to Reentrancy are guarded by proper access controls and input validation - see the Reentrancy attack class for patterns
  • Check that all state-changing functions follow the Checks-Effects-Interactions (CEI) pattern to prevent reentrancy and logic ordering bugs
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Reentrancy examples →

Sources & References

Learn to Prevent the Next Paribus

The Paribus hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial