WePiggy Hack

TOTAL LOST $400K
Low Other

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain 2021 Incident surface
Recovered - No recovery reported
All-Time Rank #1067 By amount stolen
Auditors 1 Prior security audit

Incident Overview

WePiggy-OEC protocol experienced a short-term error in the CHE oracle, causing the CHE price in WePiggy to be much higher than the market price, and resulting in abnormal liquidations for users who borrowed CHE assets. Based on prices at the time of the incident, the total loss of user assets was approximately US$400,000.

The price of CHE surged from the normal US$0.28 to a maximum of US$33,486,904.70

All abnormal liquidating transactions:

https://www.oklink.com/zh-cn/oec/tx/0xe9651ee3…245295

https://www.oklink.com/zh-cn/oec/tx/0x07727fba…90f3c9

https://www.oklink.com/zh-cn/oec/tx/0xab489d06…6f5319

https://www.oklink.com/zh- cn/oec/tx/0xec53bc8d…7a0122

https://www.oklink.com/zh-cn/oec/tx/0x9b1c3aef…af9fe8

https://www.oklink.com/zh-cn/oec/tx/0x7ad59f19…2ca82e

https://www.oklink.com/zh-cn/oec/tx/0x77e49db8…4c95d2

https://www.oklink.com/zh-cn/oec/tx/0xb3940113…10116c

https://www.oklink.com/zh-cn/oec/tx/0x57b7c656…1151ab

Affected user addresses:

0x15B8a631…0dA07C

0x76179cc1…a69d40

0x53a8ba05…C09e73

List of lost funds:

1.78975414 BTC

2.221780053 ETH

301,310.5381 USDT

173.6123858 OKT

Incident Report

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

Protocol Information

Protocol Type Lending
Official Website www.wepiggy.com/
Protocol Twitter/X @wepiggydotcom
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 WePiggy'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? Likely — with a thorough Other audit checklist and test coverage
Audited by Audit Report 1 — still lost $400K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • 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

Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

DeFiTuna $570K
Other
Cascade $1.3M
Other
Lumi Finance $264K
Other
Hinkal $820K
Other
AIDCToken $121K
Other
Polymarket $3.0M
Other

Learn to Prevent the Next WePiggy

The WePiggy 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.

Start Free Trial Browse Attack Library
Recreate exploit patterns safely Free Trial