Prediction market Polymarket briefly halted trading on its international platform on Thursday, October 29, after hackers used a hijacked third-party script to drain about $2.7 million from traders' accounts. The attack did not break into Polymarket's smart contracts. Instead, it rode in through a small piece of code the site loaded from an outside vendor, and turned ordinary logged-in browser sessions into a theft tool.

A page-speed script turned malicious

The script belonged to DebugBear, a UK-based website performance company whose real-user monitoring tool measures how fast pages load for real visitors. Polymarket embedded DebugBear's script so it could track page speed, but that script runs in every visitor's browser with the same access as Polymarket's own code.

On October 29, the file served from DebugBear's content delivery address was replaced with malicious code. DebugBear said its DNS records were compromised through its domain registrar, and it told customers using its monitoring product to remove the embed code. Researchers at Hudson Rock downloaded the malicious file on October 29 from the same address Polymarket's site used to load the script, and independent researchers found a different server answering for DebugBear's web addresses while the malicious file was still live. By November 1, the address that served the malicious file had no DNS record at all.

How the theft worked

The code reused access a signed-in trader already had in an open Polymarket page. According to Hudson Rock's review of the file, it read account details Polymarket keeps in the browser, including trading API keys, then took one of two paths. For accounts signed in with their own crypto wallet, it moved positions straight to the hackers' wallet. For accounts signed in by email, it sold positions at ever-worse prices and then moved the money out.

Blockchain records show crypto worth about $2.64 million reached the hackers' wallet in under an hour, and analytics firm Bitquery counted 985 unauthorized withdrawals between 17:10 and 18:10 UTC. The losses were uneven: four accounts accounted for roughly 43 percent of the stolen funds, while 276 users lost less than $100 each.

Polymarket posted its first status update about unauthorized activity in user wallets at 17:38 UTC, put the exchange into cancel-only mode at 18:05 UTC with relayer actions paused, and said it removed the script within the hour. Its separate US platform was not affected.

$3.9 million going back to traders

Polymarket says it is refunding about $2.7 million to 726 affected wallets, and paying another $1.19 million to about 5,500 wallets that lost money during the trading pause or had positions taken, $3.9 million in total, with no claims or tickets needed. By October 30, 689 of the 726 affected wallets had been refunded in full, with the remaining 37 being paid as they were checked. Traders whose losses were below $10,000 were due to be refunded by October 30, while larger losses required a release form.

The company said it referred the incident to UK law enforcement. It is the platform's second vendor breach this year: a similar incident in June 2026 reportedly cost traders more than $2 million. The episode is a reminder that a website's security is only as strong as the third-party code it loads. A script meant to measure page speed ended up measuring, and then moving, traders' money.