Skip to content

Which companies just had a verified incident, who lends to them and who owns them. Every claim carries its evidence level and its source. How we decide what is confirmed

DFX Cyber DeskDevelopingprediction market / web supply chain · Global (U.S.-linked platform)

Polymarket returns $3.9M to traders after hijacked DebugBear script drained wallets

On 2026-10-29 a tampered performance-monitoring script on polymarket.com sold traders' positions and moved funds to an attacker wallet. DebugBear, the script's vendor, says its DNS records were compromised through its domain registrar.

Published · 3 min read · 6 sources

What happened

On 2026-10-29 Polymarket identified unauthorized activity affecting user wallets. Its postmortem says a third-party vendor whose performance-monitoring script loaded on polymarket.com was compromised, and that the attacker swapped in a script that used active user sessions to sell positions and move funds out of wallets. Polymarket says only some users who had the site open during the window were affected.1

Hudson Rock identified the script as malicious JavaScript served from cdn.debugbear[.]com, the address Polymarket's site used for DebugBear's real user monitoring (RUM) product, and found a Polymarket build whose commit message removed the DebugBear RUM script. Polymarket has not named the vendor itself, according to SecurityWeek.4,5,6

According to BleepingComputer's analysis of a copy of the script, it checked whether a visitor was logged in, read balances and positions, and depending on how the user authenticated either sold positions or transferred prediction-market tokens to the attacker wallet, reporting results to data.debugbear.com. The Hacker News reports that wallet-connected accounts had positions moved directly, while email-login accounts had positions sold at progressively worse prices before funds were moved. Hudson Rock found no code sending passwords, seed phrases or private keys to the server.2,4,6

How the script was hijacked

DebugBear said on X that its DNS server records were compromised through its domain registrar. It described its findings as preliminary, said the attackers appear to have targeted one customer's website, said it found no indication its internal systems were compromised, and told RUM customers to remove its embed code. It did not name the registrar or explain how registrar-level access was obtained.2,4

Matt Kirkland, founder of Ohey, told RuntimeWire that a registry update to DebugBear's domain came nine minutes before DebugBear's script host began failing and 25 minutes before the first funds reached the drainer's wallet. The Hacker News reports Ohey also saw a different server answering for DebugBear's addresses at 18:13 UTC while the malicious file was still online.3,2

Who is behind it

No attribution has been made public. Hudson Rock said the evidence does not identify an attacker. Polymarket says it referred the case to law enforcement and is running its own investigation into the threat actor.5,1

Financial and operational impact

Polymarket says it is returning USD 3.9M to traders: USD 2.7M for drained wallets and positions sold or moved during the attack, including slippage, and USD 1.2M for losses during the trading pause, measured from each position's value at the pause. SecurityWeek and The Hacker News put the pause-related payment at USD 1.19M to about 5,500 wallets.1,4,2

Estimates of what reached the attacker differ by method and time of measurement. Hudson Rock reported the attacker wallet held about USD 2.19M at the time of its investigation. BleepingComputer found about 28.6 million POL, roughly USD 2.57M, moved from that wallet to three other wallets. DefiPrime valued the POL at about USD 2.64M at 18:19 UTC, per The Hacker News. Polymarket's USD 2.7M figure is the amount it is refunding.6,2,1

Polymarket put its exchange in cancel-only mode and paused relayer actions at 18:05 UTC. Its status page shows the incident identified at 17:38 UTC and resolved at 18:06 UTC, with the web app and account access components back to operational. BleepingComputer reports trading resumed about one hour after the initial suspension.2,1,6

Response and recovery

Polymarket says it removed the compromised script, cleared all caches, paused trading and the relayer, reset all active login sessions and reopened trading once the site was clean. By 2026-10-30, 95% of affected wallets had been refunded in full; The Hacker News and SecurityWeek report 689 of 726 wallets, with the remaining 37 pending verification. Eligible wallets were identified from on-chain and trading data, so no claim is needed, and a form exists for disputes.1,2,4

Polymarket says it is redeploying third-party scripts with stronger Content Security Policy, explicit version pinning, sandboxing and continuous monitoring. Hudson Rock recommended that sites keep unneeded third-party code off trading or signing pages and use Subresource Integrity where possible.1,2

What investors and lenders should watch

Polymarket is funding the refunds itself rather than passing the loss to traders. SecurityWeek reports an earlier incident in June 2026, in which a third-party vendor compromise injected malicious script into Polymarket's frontend, with reported theft of around USD 3M.1,4

Open items are DebugBear's explanation of how its registrar account was compromised, whether any other DebugBear customer was targeted, and the outcome of Polymarket's law enforcement referral.4,1

The Record notes Polymarket was barred from the U.S. until 2025 and remains banned in several countries, including France and Brazil.5

What is not known

  • How DebugBear's registrar account was compromised, and which registrar is involved.
  • Who carried out the attack; no attribution has been made public.
  • Whether any other DebugBear customer was targeted beyond the one site DebugBear's preliminary findings point to.
  • Whether any stolen funds have been recovered.

Timeline

  1. Registry update to DebugBear's domain, 25 minutes before first funds reached the drainer's wallet, per Ohey's Matt Kirkland.3

  2. Attacker wallet receives first funds at 17:10 UTC and last at 18:02 UTC, per Ohey.2

  3. Polymarket posts first status update on unauthorized activity at 17:38 UTC.1,2

  4. Exchange set to cancel-only and relayer paused at 18:05 UTC; incident marked resolved at 18:06 UTC.2,1

  5. DebugBear confirms an ongoing security incident and tells RUM customers to remove its embed code.6,5

  6. Polymarket publishes postmortem: USD 3.9M being returned, 95% of affected wallets refunded in full.1

  7. SecurityWeek reports DebugBear's statement that its DNS records were compromised through its domain registrar.4

Video and further coverage

Reading video and press coverage...

Sources

  1. 1.Security incident: 3rd party vendor compromised (postmortem)Polymarket status page, 2026-10-30 · primary
  2. 2.Hackers Steal About $2.7 Million From Polymarket Traders via Hijacked DebugBear ScriptThe Hacker News, 2026-11-01 · press
  3. 3.DebugBear's domain record changed minutes before the Polymarket drain, researcher saysRuntimeWire, 2026-10-31 · press
  4. 4.Polymarket Returns $3.9 Million to Traders as DebugBear Cites DNS HijackSecurityWeek, 2026-11-02 · press
  5. 5.Polymarket confirms cyberattack on third-party provider after outagesThe Record by Recorded Future News, 2026-10-30 · press
  6. 6.Polymarket halts trading after crypto-draining script breach, $2.5M tracedBleepingComputer, 2026-10-29 · press
Cite this report

DFX Cyber Desk, "Polymarket returns $3.9M to traders after hijacked DebugBear script drained wallets," DFX Intelligence, published 2026-11-19, https://dfxintel.com/cyber/reports/polymarket-debugbear

DFX Cyber Desk reports state only what the cited sources say. A ransomware group's claim is reported as a claim, losses are reported only as a source states them, and nothing is attributed without a named source. Methodology