On-chain investigator ZachXBT raised an alarm on May 22, 2026, flagging what appeared to be a targeted breach of Polymarket’s UMA CTF Adapter contract on Polygon.
The incident drained more than $520,000 from two wallet addresses.
The platform says user funds remain safe and that the root cause was a compromised internal private key, not a flaw in its core smart contracts.
Polymarket is the largest decentralized prediction market by volume. It lets users bet on real-world events using USDC-backed tokens on the Polygon blockchain.
The UMA CTF Adapter sits at the heart of how those markets settle.
Per Polymarket’s own documentation, the adapter is the on-chain bridge connecting the Gnosis Conditional Token Framework, which underpins every Polymarket market, to UMA’s Optimistic Oracle, which verifies outcomes. If the adapter is compromised, market resolution and rewards payouts are at risk.
How Funds Left Two Addresses in Under an Hour
ZachXBT’s alert named the suspected attacker address as 0x8F98075db5d6C620e8D420A8c516E2F2059d9B91. Security firm PeckShield quickly confirmed the report. PeckShield identified two source addresses, 0x871D…9082 and 0xf61e…4805, that were each drained of their balances.
It also confirmed that part of the stolen funds had already moved to ChangeNOW, a non-custodial exchange often used to obscure fund trails.
On-chain analytics firm Bubblemaps said the attacker was removing 5,000 POL tokens roughly every 30 seconds at the height of the incident. Bubblemaps put the total loss closer to $600,000 at the time of its alert.
That figure is unverified. The $520,000 figure from PeckShield, derived from the two confirmed drained addresses, is the number supported by two independent sources.
Polymarket Says Contracts Are Intact
Polymarket protocol contributor Shantikiran Chanal responded publicly within hours. He said the security reports were tied to the platform’s rewards payout activity and that early findings pointed to “a private key compromise of a wallet used for internal operations, not contracts or core infrastructure.” He added that user funds and market resolution remain safe.
That framing matters. A private key compromise means an attacker gained control of an administrative wallet rather than exploiting a bug in the contract code itself.
Notably, Polymarket’s bug bounty program, hosted on Cantina and updated in April 2026, explicitly classifies admin and operator key compromise as out of scope for high-severity rewards, citing centralization risks as a known operational trade-off.
Whether the targeted adapter serves active markets or is a legacy version is still unverified. PolygonScan records show multiple adapter contract versions from earlier deployments remain visible on-chain.
Polymarket had also introduced new smart contracts through a CLOB v2 upgrade in April 2026. It is not yet clear which adapter version the attacker targeted.
A Third Incident in Eight Months
This is not Polymarket’s first peripheral security failure. In November 2025, a phishing campaign exploited the platform’s comment sections, resulting in more than $500,000 in user losses through social engineering.
In December 2025, attackers exploited a third-party authentication provider linked to Magic Labs, draining accounts without touching the underlying smart contracts.
In each case, Polymarket maintained that core contracts remained uncompromised.
The May 22 incident follows that pattern: peripheral infrastructure breached, core protocol intact.
But the frequency of incidents raises questions about key management practices and the security of administrative wallets that hold payout authority over live markets.
Milestones Pending
No official post-mortem has been published as of the time of writing on May 22, 2026.
Polymarket has not confirmed the exact version of the adapter targeted, the total funds at risk, or whether payout operations have been paused.
UMA Protocol has not issued a separate statement.
Watchers should monitor Polymarket’s official X account and UMA Protocol’s X account for the post-mortem, which typically arrives within 24 to 72 hours of incidents of this scale.
