Polymarket briefly halted trading after a compromise at website-monitoring provider DebugBear served crypto-draining JavaScript to its users; Polymarket says it will fully reimburse affected traders
BleepingComputer reported on 29 October 2026 (US Eastern time) that prediction market platform Polymarket temporarily suspended trading after hackers compromised a third-party service to distribute cryptocurrency-draining JavaScript.
Polymarket said: "One of our third party providers was compromised, and we have referred this to relevant law enforcement," and "Anyone who has been impacted will be made whole," according to BleepingComputer. (source: BleepingComputer)
BleepingComputer says Polymarket placed its exchange into cancel-only mode at 2:05 p.m. ET (2:05 am Perth time on 30 October) and that the incident was marked resolved at 3:05 p.m. ET (3:05 am Perth time on 30 October).
Polymarket's trading account said on X at 3:00 am Perth time on 30 October (19:00 UTC, 29 October): "Trading is now fully back online. We'll make this right and are fully reimbursing all affected traders." (source: Polymarket (@PolymarketTrade) on X) According to BleepingComputer, Hudson Rock researchers identified malicious JavaScript distributed through DebugBear's CDN that was designed to steal cryptocurrency and prediction-market holdings from Polymarket users; BleepingComputer's own analysis found it was designed to hijack authenticated Polymarket trading sessions, liquidate users' prediction-market positions and transfer assets to an attacker-controlled wallet, and that the wallet transferred approximately 28.6 million POL, valued at roughly $2.57 million, to three additional wallets.
BleepingComputer says Polymarket has not disclosed how many users were affected, how much cryptocurrency was stolen, or how the reimbursement process will work. (source: BleepingComputer)
DebugBear, a website performance-monitoring service, said on X at 2:00 am Perth time on 30 October (18:00 UTC, 29 October): "We're impacted by an ongoing security incident. If you use our RUM product, please remove the embed code from your website."
In a later post it said it has engaged specialist cyber incident response support and will work with affected customers directly. (source: DebugBear on X)
- Product
- Polymarket (polymarket.com); DebugBear Real User Monitoring (RUM) JavaScript
- Versions
- n/a — third-party script compromise
- Exploited in Australia?
- unknown
- Patch to
- Sites using DebugBear RUM: remove the embed code now, as DebugBear advises, and review what the script could reach. Everyone embedding third-party JavaScript on logged-in pages: restrict it with a Content Security Policy and Subresource Integrity where possible, and keep an inventory of who can change code on your pages. Polymarket users: check your positions and wallet history, and rely only on official Polymarket channels about reimbursement.
- Primary: BleepingComputer — Polymarket halts trading after crypto-draining script breach, $2.5M traced (29 Oct 2026)
- Vendor: DebugBear on X — impacted by an ongoing security incident; remove the RUM embed code (30 Oct 2026, 2:00 am AWST)
- Source: Polymarket (@PolymarketTrade) on X — trading fully back online; reimbursing affected traders (30 Oct 2026, 3:00 am AWST)
- Source: DebugBear on X — engaged specialist cyber incident response support (30 Oct 2026, 6:16 am AWST)
