VeloraDEX Hack

TOTAL LOST $20K
Low Other

Summarize with AI

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

Incident Overview

On 7th October 2025, an attacker exploited a known vulnerability in VeloraDEX's (formerly ParaSwap) Augustus V6 contract, stealing approximately $20,000 in USDC from a victim who had previously approved the vulnerable contract. This exploit occurred despite VeloraDEX having previously conducted a white hat operation to secure user funds and publicly warning users to revoke permissions to the Augustus V6 contract.

The vulnerability existed in the Augustus V6 contract, which VeloraDEX had previously identified and attempted to mitigate through a white hat operation that secured funds for at-risk users. Despite pausing the V6 API and conducting the protective measures, users who had granted token approvals to the Augustus V6 contract remained exposed. The attacker exploited these lingering approvals to drain USDC tokens from victims who had not revoked their permissions.

VeloraDEX had previously secured recovered funds in a Safe Wallet and issued public warnings urging users to revoke permissions, but some users either missed the warning or failed to take action. The victim in this instance lost approximately $20,000 in USDC, representing one of the missed addresses from the original white hat recovery effort where 4 addresses collectively lost $24,000.

Attacker Address:

0xcc3a5dc0…d5c481

Victim Address:

0x05808cf9…9a339e

Exploit Transaction:

0x5b1e67ed…4f70de

Incident Report

Protocol / Project VeloraDEX
Date of Incident
Attack Technique Other
Classification Exchange (DEX)
Primary Source View Post-Mortem

Protocol Information

Protocol Type DEX Aggregator
Official Website www.velora.xyz/
Protocol Twitter/X @VeloraDEX
Team Anonymous
Source Code Unverified

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 other 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 VeloraDEX's contract logic - root cause: exchange (dex)
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? Likely — with a thorough Other audit checklist and test coverage
Audited by Audit Report 1 — still lost $20K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Other are guarded by proper access controls and input validation
  • 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

Sources & References

Learn to Prevent the Next VeloraDEX

The VeloraDEX 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