Polymarket traders drained through a compromised DebugBear script: if your site uses DebugBear, remove it
Polymarket said a third-party provider was compromised on 29 Oct 2026. Researchers say a DebugBear monitoring script was swapped for a wallet drainer that acted on logged-in traders. Estimates of the loss are near 2.6 million dollars. Here is what to check.
Updated 2 Nov 2026: see what changedHow urgent
Act now
Who is affected
Sites that load a DebugBear monitoring script, and Polymarket traders (Polymarket says its US platform did not appear to be affected). Researchers say the swapped script acted on logged-in Polymarket sessions
What to do
If your site loads a DebugBear script, remove it until DebugBear says it is safe, then list every third-party script on your site. If you trade on Polymarket, check your wallet activity and wait for Polymarket's reimbursement notice
Published 30 Oct 2026 · Sources last checked 2 Nov 2026No. 22 / 87
Updates, follow-ups and corrections
- Update · 2 Nov 2026. SecurityWeek reports that DebugBear now says its DNS records were compromised through its domain registrar and that attackers appear to have targeted one customer, a preliminary finding. Polymarket said on 30 Oct that 726 wallets were affected and that it is reimbursing traders, about 3.9 million dollars in total according to SecurityWeek, and that it will share a postmortem. DebugBear has not explained how the registrar was breached. We read this through SecurityWeek, not DebugBear or Polymarket directly.
We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.
What happened
On Thursday 29 October 2026, Polymarket halted trading on its international platform for nearly an hour after reports of drained wallets. It said that "one of our 3rd party providers was compromised", that it had "identified and fixed an issue", and that trading was back at 3 p.m. ET. Polymarket did not name the provider. A person familiar with the matter told NBC News that the attackers reached funds through software from DebugBear, a website performance and analytics tool, and DebugBear said on X that it was experiencing an "ongoing security incident".
An independent researcher, Ohey, compared archived copies of the script and reports that the DebugBear file loaded by Polymarket was replaced by a different, smaller file that acted as a wallet drainer. According to that analysis, it ran only in logged-in sessions, read data Polymarket keeps in the browser, and used Polymarket's own order client to sign and send transfers. Researchers' timelines show Polymarket shipping a release that removed the script, and DebugBear telling its monitoring customers to remove its embed code.
Who is affected
- Any site that loads a DebugBear monitoring script. We do not know whether other DebugBear customers were affected.
- Polymarket traders on the international platform. Polymarket says it will reimburse all affected traders ("we'll make this right and are fully reimbursing all affected traders") and says the US platform did not appear to be affected. The Block, citing Arkham, put the amount at about 2.65 million dollars; other estimates are near 2.6 to 2.7 million. Polymarket has not published a figure.
What to do
- If your site loads a DebugBear script, remove it until DebugBear says it is safe. Check DebugBear's own status page or posts for the official instruction, and review your logs for that period.
- List every third-party script your site loads, who owns it, and why it is there. Start with pages where people log in or pay.
- Traders: review your wallet activity, be wary of unexpected signature requests, and wait for Polymarket's reimbursement notice instead of following links from messages.
If you build with AI tools
Our advice, not from the reports:
- Keep analytics and monitoring scripts off pages that handle logins, payments or wallets, or load them in a sandboxed frame.
- Pin scripts with integrity hashes (Subresource Integrity) where the vendor's file does not change. A monitoring script that its vendor updates often cannot be pinned easily, which is a reason to keep it off sensitive pages.
- Limit which hosts your pages can send data to with a Content Security Policy (the
connect-srcsetting). In this case, researchers note that every host the drainer called, except DebugBear's, was already allowed by Polymarket's policy, so a policy only helps if it is as narrow as the page needs. - Have a way to remove a third-party script quickly and deploy a clean build.
What we could not confirm
We read Polymarket's statements through NBC News and did not read DebugBear's post directly. Naming DebugBear comes from a person familiar with the matter and from researchers, not from Polymarket. We do not know how DebugBear was compromised, how long the bad script was active, or who is behind it (Polymarket said the attack appeared to come from the United Kingdom and referred it to British law enforcement). The technical details come from one researcher's analysis, which we have not verified. Neither company has published a post-mortem yet, and we will update this page when one appears.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- NBC News: Polymarket pauses trading amid reports of users' wallets drained (29 Oct 2026, press report that quotes Polymarket's posts on X) (opens in a new tab)
- Ohey: Polymarket wallet drainer served from DebugBear's script CDN (29 Oct 2026, independent researcher analysis, not verified by us) (opens in a new tab)
- Genfinity: Polymarket hack, compromised DebugBear script drains roughly 2.6 million dollars from traders (29 Oct 2026, press report) (opens in a new tab)
- TechCrunch: Binance pauses withdrawals as hackers suspected of stealing billions in crypto (29 Oct 2026, press report, mentions the Polymarket incident) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.