BlockBeats report: On May 22, Josh Stevens, Vice President of Engineering at Polymarket, posted that, with assistance from ZachXBT, BitcoinVN, and ChangeNOW, $164,000 of the stolen funds from the Polymarket private key compromise has been frozen, accounting for approximately 28.6% of the total $573,200 transferred. The incident did not affect Polymarket or UMA smart contracts; user funds remain secure, and platform operations continue normally. The investigation revealed that the breach stemmed from a private key that had existed for approximately six years and was used for internal deposit configurations, resulting in funds being continuously sent to the compromised address. The relevant teams are continuing to track the remaining stolen funds.
Polymarket Freezes $164,000 in Stolen Funds Following Private Key Leak
KuCoinFlashShare
Summary
On-chain news outlet Blockbeats reported on May 22, 2026, that Polymarket’s Engineering VP Josh Stevens confirmed that $164,000 in stolen funds from a private key leak has been frozen. ZachXBT, BitcoinVN, and ChangeNOW assisted in the recovery. The amount represents 28.6% of the total $573,200. The breach involved a six-year-old key used for internal recharge settings. No impact on Polymarket or UMA smart contracts was observed, and user funds remain secure. The team is tracking the remaining stolen assets. Crypto news platforms continue to monitor the situation closely.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.