Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: polymarket (2 articles)Clear

Hijacked DebugBear monitoring script drains about 2.7 million dollars from Polymarket trader wallets

Hudson Rock and Ohey reported that attackers hijacked DebugBear, a real user monitoring vendor whose page-speed script Polymarket loaded, by compromising its DNS through the domain registrar rather than breaching DebugBear itself. A malicious server answered for DebugBear's addresses and served code that reused a signed-in trader's session to read stored trading API keys and move positions to the attacker, selling at worsening prices for email-login accounts. Polymarket says 726 wallets were affected and about 2.64 million dollars in POL reached the attacker within an hour, and it is returning 3.9 million dollars in total. No keys or seed phrases were exfiltrated.

Check
Inventory third-party scripts on pages that handle signing or trading, pin them with Subresource Integrity, and remove any not strictly needed.
Affected
Sites loading third-party scripts on authenticated trading or signing pages can have those scripts swapped via vendor DNS compromise to hijack sessions and move funds.
Fix
Enforce a strict content security policy and Subresource Integrity, pin and sandbox third-party scripts, and have users reject unexpected signing requests.

Polymarket users lose nearly $3 million in website supply-chain attack

The crypto prediction market Polymarket says attackers stole close to $3 million from users after compromising a third-party vendor and injecting a malicious script into the platform's website. The script ran on the live site and prompted users connecting their wallets to approve transactions that drained their funds; researchers traced roughly $2.94 million taken from around a dozen accounts and bridged into Ethereum. Because the attack rode in through a trusted frontend dependency rather than Polymarket's own systems, it was invisible to users. Polymarket removed the dependency, contained the incident, and pledged full refunds. It was the platform's second security incident in two months.

Check
Review the third-party scripts and dependencies loaded by your web frontends, and confirm you would detect unauthorized changes to them; users should be wary of unexpected wallet-signing prompts.
Affected
Web platforms that load third-party frontend dependencies, and their users; a single compromised vendor can inject wallet-draining or credential-stealing code that runs as trusted, first-party code in the browser.
Fix
Pin and integrity-check third-party scripts with Subresource Integrity, monitor frontend code for unauthorized changes, vet and limit vendor dependencies, and warn users to scrutinize every wallet-signing or credential prompt.