Polymarket private key leak incident has frozen $164k in funds

robot
Abstract generation in progress
Mars Finance news: Polymarket engineering vice president Josh Stevens disclosed that, with the assistance of ZachXBT, BitcoinVN, and ChangeNOW, $164,000 in funds has already been frozen in the Polymarket private key leak incident, accounting for about 28.6% of the total $572,000 transferred. Josh said this incident did not affect Polymarket or UMA smart contracts; users’ funds are safe and the platform is operating normally. The investigation shows the incident was caused by a private key that has existed for about 6 years being leaked; the private key was used for internal recharge configuration, causing funds to be continuously sent to the affected address. Currently, the relevant teams are continuing to track the destination of the remaining stolen funds.
UMA-3.53%
View Original
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.
  • Reward
  • 9
  • 2
  • Share
Comment
Add a comment
Add a comment
MoonlightColdWallet
· 3h ago
ChangeNOW cooperating with freezing? Rarely is a CEX this proactive
View OriginalReply0
MosaicBow
· 4h ago
ZachXBT is back at it again; the on-chain detective lives up to its reputation.
View OriginalReply0
GateUser-04e4dac2
· 14h ago
Keeping the private key for 6 years without changing it raises serious security concerns.
View OriginalReply0
VolatilityInATeacup
· 14h ago
BitcoinVN this time coordinated quite quickly, the efficiency over in Vietnam is good
View OriginalReply0
雾里看TVL
· 14h ago
The Vice President of Engineering personally disclosed, giving full marks for transparency
View OriginalReply0
0xCaffeine
· 14h ago
UMA oracle was unaffected, DeFi Lego stability is still okay.
View OriginalReply0
GateUser-9008328f
· 14h ago
Polymarket contracts were unaffected, which is a relief; users don't need to panic.
View OriginalReply0
ReorgSurvivor
· 14h ago
Internal recharge configuration uses a private key; isn't this design inherently problematic?
View OriginalReply0
RouterRunner
· 14h ago
Tracking remaining funds? Mixing services are basically a dead end.
View OriginalReply0
View More
  • Pinned