Radiant Capital Hack

TOTAL LOST $4.3M
Medium Flash Loan Attack

Summarize with AI

Affected Chain 2024 Incident surface
Recovered - No recovery reported
All-Time Rank #465 By amount stolen
Auditors 1 Prior security audit

Incident Overview

Radiant Capital suffers $4.5 million loss in ETH due to flash loan attack.

On January 2, 2024, Radiant Capital, a multichain lending protocol, was attacked through a flash loan exploit, resulting in the theft of over 1,900 ETH, valued at over $4.5 million. The attacker exploited a vulnerability in the project's token quantity calculation, involving precision expansion and rounding. By controlling the precision and using rounding to expand profit margins, the attacker drained all USDC from the pool.

As of the time of writing, the stolen 1,902 ETH remains in the hacker's address without any movement.

Attacker address:

https://arbiscan.io/address/0x826d5f4d…9dde6d

Malicious transactions:

https://arbiscan.io/tx/0x1ce7e9a9…4c7c9b

https://arbiscan.io/tx/0x2af55638…d14243

https://arbiscan.io/tx/0xc5c4bbdd…77fc6d

Malicious contract:

https://arbiscan.io/address/0x39519c02…8faa8f

Incident Report

Protocol / Project Radiant Capital
Date of Incident
Attack Technique Flash Loan Attack
Classification Borrowing and Lending
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Affected Token RDNT
Official Website radiant.capital/
Protocol Twitter/X @RDNTCapital
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
DeFi Ethereum Ecosystem Binance Launchpool YZi Labs Portfolio Lending & Borrowing Arbitrum Ecosystem BNB Chain Ecosystem Base 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 flash loan attack and Solidity and EVM internals
Capital Required Flash loan capital (borrowed atomically, zero upfront cost)
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Radiant Capital'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 Flash Loan Attack vulnerabilities in code review
Audited by Audit Report 1 — still lost $4.3M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Radiant Capital, these are the critical security checks that could have prevented this incident (January 2024).

  • Verify all logic paths related to Flash Loan Attack are guarded by proper access controls and input validation - see the Flash Loans Attacks attack class for patterns
  • 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

Security Audit History

Bug Bounty Immunefi Details

Related Attack Classes

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

See all Flash Loans Attacks examples →

Sources & References

Learn to Prevent the Next Radiant Capital

The Radiant Capital 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