Breaking Security Alert Today! According to PeckShield monitoring, a whale user’s multi-signature wallet was hacked due to private key leakage, resulting in a loss of approximately $27.3 million (including ETH and other assets). The hacker acted swiftly, laundering $12.6 million (about 4,100 ETH) through TornadoCash, and holding about $2 million in liquid assets. More seriously, the hacker has gained full control of the victim’s multi-signature wallet — which held a high-leverage long position on Aave: collateralized $25 million in ETH and borrowed 12.3 million DAI. Malicious actions by the hacker could trigger further liquidation losses!
Key Details of the Incident
Item
Details
Amount/Quantity
Total Loss
Multi-signature wallet private key leaked and stolen
≈$27.3 million
Laundered Funds
Through TornadoCash
$12.6 million (4,100 ETH)
Hacker’s Remaining Liquid Assets
Holding cash/tokens
≈$2 million
Victim Wallet Leverage Position
Aave platform long position
Collateralized $25 million ETH, borrowed 12.3 million DAI
Hacker Control
Fully took over the multi-signature wallet
Can operate the position, potential liquidation risk
Data Source: PeckShieldAlert real-time monitoring (December 18, 2025)
Incident Review and Risk Analysis
Cause of Attack: Private key leakage (multi-signature wallets should be more secure, but if a single private key or threshold key leaks, hackers can bypass security).
Hacker’s Path: Rapid asset transfer → laundering via TornadoCash → retaining some liquid funds.
Major Hidden Risks: Hacker controls the multi-signature wallet, can operate Aave leverage positions at will. Malicious withdrawal of collateral or borrowing more stablecoins could trigger chain liquidations, further amplifying losses.
Current Status: No signs of large-scale liquidation of the victim’s position yet, but the risk is extremely high. The community has called on protocols like Aave to remain vigilant.
This is one of several whale-level security incidents in the second half of 2025, ranking among the largest losses.
Security Reminder: Whales Need to Be More Cautious
Multi-signature is Not Foolproof: Improper threshold settings or negligence in private key management can still be exploited.
Leverage Must Be Cautious: High collateralized borrowing positions can exponentially increase losses if wallets are compromised.
Private Key Management: Avoid storing on a single device, use hardware wallets + air-gapped devices, rotate keys regularly.
Anomaly Monitoring: Enable real-time alerts (e.g., PeckShield, MistTrack) for early detection and stop-loss.
There is no absolute security in the crypto world, only more rigorous risk control. Whales may sink, but retail investors should learn lessons — safety of principal always comes first.
What do you think about this incident? Share your thoughts in the comments section~
A. Private key management is too difficult, preparing to reduce positions
B. Multi-signature + hardware wallet is enough for security
C. Leverage is too dangerous, preparing to deleverage
D. Normal, common in the crypto space
Take one step at a time — but never skip the security step!
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
Whale multi-signature wallet private key leaked! $27.3 million stolen overnight, hackers have laundered $12.6 million
Breaking Security Alert Today! According to PeckShield monitoring, a whale user’s multi-signature wallet was hacked due to private key leakage, resulting in a loss of approximately $27.3 million (including ETH and other assets). The hacker acted swiftly, laundering $12.6 million (about 4,100 ETH) through TornadoCash, and holding about $2 million in liquid assets. More seriously, the hacker has gained full control of the victim’s multi-signature wallet — which held a high-leverage long position on Aave: collateralized $25 million in ETH and borrowed 12.3 million DAI. Malicious actions by the hacker could trigger further liquidation losses!
Key Details of the Incident
Data Source: PeckShieldAlert real-time monitoring (December 18, 2025)
Incident Review and Risk Analysis
This is one of several whale-level security incidents in the second half of 2025, ranking among the largest losses.
Security Reminder: Whales Need to Be More Cautious
There is no absolute security in the crypto world, only more rigorous risk control. Whales may sink, but retail investors should learn lessons — safety of principal always comes first.
What do you think about this incident? Share your thoughts in the comments section~ A. Private key management is too difficult, preparing to reduce positions B. Multi-signature + hardware wallet is enough for security C. Leverage is too dangerous, preparing to deleverage D. Normal, common in the crypto space
Take one step at a time — but never skip the security step!