Polymarket says it will reimburse traders after a compromised third-party script drained accounts on its international platform on 29 October. Blockchain data puts the losses at between about $2.2 million and $2.65 million. Polymarket has not given its own figure.
What happened
Users began reporting drained accounts at around 17:30 UTC. Shortly after 18:00 UTC Polymarket switched its exchange to cancel-only mode and paused its relayer, then said “one of our 3rd party providers was compromised”. Trading resumed at about 3pm ET, and Polymarket’s status page marked the incident resolved at 3:05pm ET, Unchained reported.
Polymarket has not named the provider. Researchers at Hudson Rock traced the malicious code to a JavaScript file served by DebugBear, a UK-based web performance monitoring company whose real-user monitoring script ran on Polymarket’s site. DebugBear said on X it had been “impacted by an ongoing security incident” and told customers using that script to remove it, Cyber Kendra reported.
How the script drained accounts
Polymarket’s smart contracts were not touched. According to Hudson Rock’s analysis, the script read the login details, proxy wallet address and trading API keys stored in the browsers of signed-in users, then used permissions the site already had. For wallet-connected accounts it batch-transferred position tokens to the attacker. For email-login accounts it placed sell orders at falling prices and tried to move the proceeds out. It also sent each victim’s wallet address, location and portfolio value back to the attacker.
Polymarket has not said how many accounts were hit. One trader reported losing around $800,000. Arkham data shows the suspected attacker’s wallet holding close to $2.65 million in POL before the funds were moved on, The Block reported.
Refunds and next steps
“Anyone who has been impacted will be made whole,” Polymarket said, adding that it is “fully reimbursing all affected traders”. It has referred the incident to law enforcement, which Reuters reported means UK authorities, and has not said when refunds will arrive. It is the second time this year a compromised third-party dependency has been used to drain Polymarket users: a similar attack in June took around $3 million, Decrypt reported.
The attack landed in a bad week for prediction markets. Rival Kalshi was charged with felonies in Utah the day before, and reports of a hot-wallet breach at Binance followed within hours, making 29 October one of the worst days for crypto security this year.
It also shows that a platform can be compromised without its smart contracts being touched. Traders should sign out of trading sites they are not using, revoke API keys they no longer need, and treat unexpected signature requests as a red flag. Our crypto gambling guide covers the checks to run before depositing anywhere, and our prediction markets coverage follows the fallout.
Sources
- The Block: Polymarket resumes trading after $2.65 million exploit (29 October 2026)
- Unchained: Polymarket resumes trading, vows to reimburse traders (29 October 2026)
- Cyber Kendra: Polymarket hacked via DebugBear script, vendor confirms breach (October 2026)
- Decrypt: Polymarket to refund users after website exploit (June 2026)
- Reuters via Central Oregon Daily: Polymarket resumes trading after third-party security breach (29 Oct 2026)




