hack or exploit

Polymarket restricts trading to cancel-only mode amid wallet drain reports

39Importance
closedStatus
17News media
23Pieces
Published
Updated
Since then
21 new reports
Also mentions
ARKM

Polymarket halted trading, limited activity to cancel-only mode, and then reopened after saying a third-party provider had been compromised. New coverage adds different loss estimates, account counts, and several reports that Polymarket planned or promised reimbursement for affected traders.

Key claims & sources

✓
On Oct. 29, Polymarket put trading into cancel-only mode and paused relayer actions while it reviewed reports that user funds had been taken from accounts.
✓
One account of the breach said nearly 1,000 Polymarket accounts were drained and more than $2.6 million was taken.
✓
An on-chain trace estimated about $2.7 million in outflows from the incident and said trading was back online.
✓
Polymarket reopened trading at about 3 p.m. ET on Thursday and said it would fully reimburse affected traders.
✓
Polymarket said the incident came through a compromised third-party provider rather than its core infrastructure, and later said it had identified and fixed the issue.
✓
A separate report said the incident involved a compromised monitoring script on October 29 and that 726 trader wallets were drained.
✓
Polymarket later said its October 30 update put total refunds at $3.9 million, including losses tied to the trading pause.

What it means

Polymarket is the dominant crypto-native prediction market, settling wagers in USDC on Polygon and marketing itself as a transparent, on-chain alternative to traditional betting books. On Oct. 29, a monitoring library from third-party vendor DebugBear, embedded in the platform's frontend, was compromised and used to inject malicious JavaScript that intercepted trading sessions. This is a supply-chain attack, the same category that has repeatedly hit crypto sites through compromised npm packages and analytics scripts rather than smart-contract bugs.

Attackers drained roughly $2.65 to $2.7 million from more than 700 wallets before Polymarket moved the exchange into cancel-only mode, locking traders out of new buys and sells while leaving them able to close existing positions. Its October 30 update fixed total reimbursement at $3.9 million, covering both the stolen assets and collateral losses tied to the pause itself. Affected traders get made whole directly from Polymarket rather than chasing recovery through insurers or the attacker, while the company absorbs the cost.

The breach shows how a platform built around trustless, on-chain settlement can still be undone by an ordinary web-stack dependency: a performance-monitoring script no different from thousands embedded across the internet. Polymarket's contracts were untouched, but the user-facing layer that actually moves funds proved to be a single point of failure controlled by an outside vendor. That gap between decentralized settlement and centralized frontend infrastructure is the uncomfortable trade-off this incident puts on display. (per financemagnates.com)

Polymarket said it referred the incident to law enforcement, and whether the vendor is formally identified and held liable will shape whether other platforms using similar monitoring tools face the same exposure. The $3.9 million refund figure set in the October 30 update is the number to track for any revision as reconciliation across the roughly 726 affected wallets is finalized and full payouts are confirmed.

Market reaction i

Total crypto marketall crypto assets combined no single asset in the event: read against the whole market
first headline
-0.9% 2 h before
-2.0% 4 h after
$2.7Tmarket cap at publication
12data points

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Oct 29 18:12
+15 min
Oct 29 18:27
The Defiant context
Its angle: canceled, blocked, still
+22 min
Oct 29 18:35
BeInCrypto adds
Adds $1.4M, with quotes
+27 min
Oct 29 18:39
Crypto Briefing echo
No new facts: comprehensive, persistent, resolves
+29 min
Oct 29 18:41
+41 min
Oct 29 18:53
+43 min
Oct 29 18:55
+49 min
Oct 29 19:01
U.Today adds
Sharpens the figure: $2.6M
+1 h 10 m
Oct 29 19:23
+1 h 28 m
Oct 29 19:40
The Defiant adds
Sharpens the figure: $2.7M, with quotes
+1 h 52 m
Oct 29 20:04
Crypto Economy context
Its angle: 2115872225144271131, dependencies, jconorgrogan
+1 h 54 m
Oct 29 20:07
Finance Magnates echo
No new facts: announcement, suspension, responding; with quotes
+1 h 56 m
Oct 29 20:09
Unchained echo
No new facts: newsletter, impacting, featuring; with quotes
+2 h 5 m
Oct 29 20:17
CP CryptoPotato echo
No new facts: investigators, transactions, subsequently; with quotes
+3 h 12 m
Oct 29 21:25
AMBCrypto echo
No new facts: emergency, promising, prompted
+6 h 11 m
Oct 30 00:23
Crypto Economy echo
No new facts: reimbursements, introduced, preventive; with quotes
+6 h 42 m
Oct 30 00:54
Coinpedia echo
No new facts: coinpedia, history, fintech
+9 h 3 m
Oct 30 03:15
The Crypto Guardian echo our clock
No new facts: confirmation, independent, javascript; with quotes
+12 h 45 m
Oct 30 06:57
Crypto News Australia echo
No new facts: with quotes
+12 h 45 m
Oct 30 06:57
Crypto News Australia echo
No new facts: with quotes
+1 d 3 h
Oct 30 21:47
+3 d 5 h
Nov 2 00:03
NewsBTC adds our clock
Sharpens the figure: $1.2M, with quotes

Thefts of a similar size

WhenWhat happenedFigure
5.2 years ago Punk Protocol · Contract vulnerability incident $4M
10 months ago Unleash Protocol · Privilege compromise incident $3.9M
10 months ago Flow · Infinite Mint incident $3.9M
1.4 years ago ForceBridge · Improper Access Control incident $3.9M
3.6 years ago Patricio Worthalter · Phishing attack incident $3.8M

4280 incidents stored · 564 were as large as this one or larger ($3.9M)