Newsroom / Polymarket

DexSheet Newsroom Incident

Polymarket halts trading for an hour after third-party provider compromise

Users reported drained wallets on the international site. Polymarket says it is returning $3.9M: $2.7M to 726 drained wallets and $1.19M to about 5,500 wallets for losses during the trading pause. Website monitoring firm DebugBear says it was hit by a security incident the same day.

Effective Oct 29, 2026: Polymarket halts trading for an hour after third-party provider compromise. Affects: Users of the international polymarket.com site, especially those whose wallets were drained. Source: x.com, verified Oct 31, 2026. If this rules Polymarket out, our top-listed alternative is Kalshi.

Official site: kalshi.com

Trading halt (cancel-only mode) Normal trading→About 1 hour, 14:05 to 15:05 ET
Held by suspected attacker wallet (Arkham, not confirmed by Polymarket) About $2.65M in POL
Converted to POL and moved out (Bubblemaps estimate, not confirmed by Polymarket) About $2.7M; more than 700 users affected
Refunds (per Polymarket) Full reimbursement promised, no total given (29 Oct)→$3.9M: $2.7M to 726 drained wallets (689 paid by 30 Oct) plus $1.19M to about 5,500 wallets for pause losses

Polymarket put its international exchange, polymarket.com, into cancel-only mode and paused relayer actions at 14:05 ET on 29 October 2026 while it investigated an incident. It later said one of its third-party providers had been compromised, that it had fixed the issue and referred it to law enforcement, and that anyone impacted will be made whole. Its status page marked the incident resolved at 15:05 ET, and Polymarket then said trading was fully back online and that it is fully reimbursing all affected traders.

In cancel-only mode traders could cancel open orders but could not place new orders, and no trades were processed. The relayer, which submits users' signed transactions such as transfers and redemptions to the blockchain, was paused for the same window.

Polymarket has not named the provider; it later put the number of drained wallets at 726 and the amount taken from them at $2.7 million. Onchain analytics firm Bubblemaps estimated that more than 700 users were affected and that about $2.7 million was converted to POL and moved out; its overall tally of $3.46 million includes $750,000 that one trader says he moved to safety himself, so the stolen total is uncertain. Arkham data cited by The Block and Decrypt shows a wallet linked to the suspected attacker holding about $2.65 million in POL after a series of USDC.e-to-POL swaps. Researchers at Hudson Rock said a script served from DebugBear, a web performance monitoring service, contained wallet-draining code that sent funds to the same address. Polymarket has not confirmed the vendor attribution.

On 30 October at 14:37 UTC Polymarket said 689 of the 726 affected wallets had been refunded in full and that the remaining 37 are being paid as each is verified. It said it will also cover traders who lost money during the trading pause or whose positions were taken, paying $1.19 million to about 5,500 wallets starting that day, for a total of $3.9 million returned: the $2.7 million plus the pause-related losses. It said no claims or tickets are needed, that it removed the compromised provider within the hour, and that it will publish a postmortem; it still has not named the provider.

DebugBear, a website performance monitoring service, said on X at 18:00 UTC on 29 October that it was impacted by an ongoing security incident and asked customers of its real-user monitoring product to remove its embed code from their websites. A person familiar with the matter told CNBC that the Polymarket incident stemmed from the DebugBear hack and that Polymarket referred it to UK law enforcement, where DebugBear is based. CNBC also reported that Polymarket told users on Discord that those who lost less than $10,000 would have funds restored by 30 October, and that those who lost more must sign a release form to be reimbursed; Polymarket's 30 October update says no claims or tickets are needed.

This is the third reported loss of funds at Polymarket in 2026. In May a private key compromise drained about $700,000 from an internal top-up wallet, and in June a compromised third-party vendor injected malicious code into the website and took about $3 million from fewer than 15 accounts, which Polymarket said it would refund in full. The incident was reported on the international platform; Polymarket did not report any impact on Polymarket US.

“In total, we’re returning $3.9M to traders: the $2.7M plus $1.19M to cover pause-related losses.”

— Polymarket Traders on X

Who this affects

Users of the international polymarket.com site, especially those whose wallets were drained; anyone with open orders or pending transfers during the halt.

Polymarket at a glance

Polymarket is a prediction market where users trade Yes/No outcome shares on an order book. It runs two separate platforms: the international, crypto-based polymarket.com on Polygon, and Polymarket US, a fiat, CFTC-regulated exchange operated by QCX LLC. The international site also lists perpetual futures.

Full Polymarket sheet

More from the newsroom

Sources

Last checked . Fees and terms change often; the venue's own page wins if it disagrees with ours.

  1. Polymarket Traders on X: refund update (30 Oct 2026) — checked 2026-10-31
  2. Bankless: Polymarket sends $3.9M back to traders after vendor script drain — checked 2026-10-31
  3. Crypto Economy: Polymarket to refund $3.9M after malicious script drains 726 trader wallets — checked 2026-10-31
  4. Polymarket Status - Exchange in cancel-only mode and relayer actions paused (2026-10-29, resolved) — checked 2026-10-29
  5. Polymarket Traders on X - third-party provider compromised, impacted users will be made whole (2026-10-29) — checked 2026-10-29
  6. Polymarket Traders on X - trading will resume at approximately 3pm ET (2026-10-29) — checked 2026-10-29
  7. Polymarket Traders on X - trading fully back online, fully reimbursing all affected traders (2026-10-29) — checked 2026-10-29
  8. CNBC - Some Polymarket user funds stolen by hackers; exchange referring matter to U.K. authorities (2026-10-29) — checked 2026-10-30
  9. DebugBear on X - impacted by an ongoing security incident; RUM customers asked to remove embed code (2026-10-29 18:00 UTC) — checked 2026-10-30
  10. The Washington Post - Polymarket pauses international trading after outside vendor's security issue (2026-10-29) — checked 2026-10-30
  11. The Defiant - Bubblemaps Traces $2.7 Million Outflow From Polymarket Breach (2026-10-29) — checked 2026-10-29
  12. The Block - Polymarket pauses trading after $2.65 million exploit, says third-party provider was compromised (2026-10-29) — checked 2026-10-29
  13. Decrypt - Polymarket Pauses Trading as Prediction Market Investigates Security Incident (2026-10-29) — checked 2026-10-29
  14. The Defiant - Polymarket Says Issue Fixed, Pledges to Make Affected Users Whole (2026-10-29) — checked 2026-10-29
  15. Hudson Rock (InfoStealers) - Polymarket Breach Alert: Wallet-Draining Code Found in a Third-Party Script (2026-10-29) — checked 2026-10-29
  16. Decrypt - Polymarket to Refund Users After Scammers Swipe Millions in Website Exploit (2026-06-25) — checked 2026-10-29

About DexSheet

DexSheet is an independent fee sheet for on-chain trading. It tracks the fees, custody, backers, incidents and availability of 96 crypto trading venues, with a dated source for every number. Every newsroom entry is checked against the venue's own announcement, docs or terms before it is published. Data: fees.json (CC BY 4.0) · RSS.