The Hacker Newsinfo@thehackernews.com (The Hacker News)
Polymarket Traders Lose $2.7 Million in Script Hijack
Part of the Polymarket story · since 30 Oct
- Fri 30 Oct, 03:00 UTC. SecurityOnline, first report. Compromised analytics script drains Polymarket trader wallets.
- Fri 30 Oct, 10:30 UTC. SecurityWeek, its first report on the story. Malicious DebugBear Script Drains Millions From Polymarket Traders.
- Sun 1 Nov, 08:30 UTC. The Hacker News, its first report on the story. Polymarket Traders Lose $2.7 Million in Script Hijack. This article, 3rd of 3.
Malicious code on Polymarket’s site substituted a page-speed script loaded from DebugBear, a real-user monitoring tool, and enabled unauthorised access to users’ open trading sessions on 29 October 2026. Hudson Rock’s review of the embedded file showed it re-used a trader’s browser-held account details and trading API keys to identify the signing and ordering components on Polymarket’s site, then redirected the signing requests to Polymarket’s relayer.
In practice, accounts signed in with a crypto wallet had their positions moved directly to the attackers’ wallet, while accounts signed in via email faced a dumping of positions at unfavourable prices before funds were withdrawn.
Blockchain tracing by Ohey tracked the attacker wallet receiving the initial funds between 17:10 and 18:02 UTC, accumulating 28.6 million POL tokens and positions from 33 wallets; by 18:19 UTC those POL tokens were worth about $2.64 million, according to DefiLlama’s price. The same wallet then sent the funds to three other addresses between 18:28 and 18:38 UTC.
Polymarket disclosed the incident publicly, stating it began removing the compromised script within the hour, paused relayer actions and trading, and referred the case to law enforcement. By 30 October, 689 of 726 affected wallets had been refunded in full, with a further $1.19 million paid to about 5,500 traders who lost money during the trading pause or had positions drained, bringing the total refunds to $3.9 million.
Polymarket urged traders to check status updates via its page and to file claims if necessary. DebugBear advised its customers to remove the compromised embed code, and Polymarket indicated it would reintroduce third‑party scripts with tighter controls, including stronger Content Security Policy, pinned versions, and sandboxing. Hudson Rock recommended removing unnecessary third‑party code from trading pages, employing Subresource Integrity where possible, and ensuring traders reject unexpected signing requests.
How the story developed
3 articles from 3 outlets since 30 Oct. Still developing; the latest report was 1 hour ago. This was the 3rd report, 2 days after the first.
- Fri 30 Oct, 03:00 UTC. SecurityOnline, first report. Compromised analytics script drains Polymarket trader wallets.
- Fri 30 Oct, 10:30 UTC. SecurityWeek, its first report on the story. Malicious DebugBear Script Drains Millions From Polymarket Traders.
- Sun 1 Nov, 08:30 UTC. The Hacker News, its first report on the story. Polymarket Traders Lose $2.7 Million in Script Hijack. This article, 3rd of 3.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 3 articles as a listHide the list
- Fri 30 OctDay 02
- Compromised analytics script drains Polymarket trader wallets03:00 · SecurityOnline · First report
- Malicious DebugBear Script Drains Millions From Polymarket Traders10:30 · SecurityWeek
Quiet for 2 days
Sun 1 NovDay 21- Polymarket Traders Lose $2.7 Million in Script Hijack08:30 · The Hacker News · This article, 3rd of 3