Home
/
News updates
/
Latest news
/

Polymarket suffered supply chain attack: $800k stolen

Polymarket Hit by Supply Chain Attack | Negligence Sparks Outrage

By

Emma Russo

Nov 9, 2026, 11:12 PM

Updated

Nov 10, 2026, 12:28 AM

2 minutes reading time

A graphic showing a hacker stealing funds from wallets, visualizing the supply chain attack on Polymarket, with warning signs in the background.
popular

A serious breach at Polymarket has shaken the crypto community as a third-party script siphoned over $800,000 from user wallets. Security experts at Hudson Rock flagged the vulnerability, leading to intense criticism over the exchange's practices and handling of user funds.

What Went Wrong?

Polymarket used DebugBear RUM, a performance-monitoring tool, and a malicious payload was inserted into the toolโ€™s script. This allowed attackers to drain funds directly from user accounts. As one user pointed out, "This is Polymarket's negligence, not DebugBear's," highlighting that the integration lacked necessary security checks.

How the Attack Worked

The malicious script operated by:

  • Identifying active user sessions.

  • Interacting with Polymarketโ€™s trading client and wallet signers.

  • Liquidating positions and funneling funds to a wallet controlled by the attackers.

At least one trader reported losses of $800,000, but total damages could exceed $2 million, sparking fears of further thefts.

Community Concerns and Criticism

Discussion across forums reveals deep dissatisfaction.

  • One commenter stated, "Loading third-party scripts without security checks is crazy business."

  • Another echoed the need for accountability, remarking that the loss was minor compared to the profits Polymarket is likely making.

Users express doubt about the platformโ€™s ability to recover trust and retain its user base if there is no effective resolution.

Official Response and Prevention Measures

Polymarket has now removed the DebugBear script entirely, yet important details about the attackโ€™s origin and how many affected sessions exist remain unconfirmed. The exchange urged users to:

  • Check Polymarket activity: Validate order history and balances.

  • Review wallet approvals: Use services like Revoke.cash to cancel suspicious permissions.

  • Clear cache and cookies: This stops potential re-execution of harmful scripts.

Implications of the Breach

Experts believe this incident may lead to stricter oversight in the crypto sector, particularly regarding third-party integrations.

Key Points to Consider

  • ๐Ÿšจ Stolen amounts exceed $800,000 and might continue to escalate.

  • โš ๏ธ Users are doubtful about Polymarket's trust recovery commitments.

  • ๐Ÿ’ก Continuous monitoring of wallet connections is critical after this incident.

While the crypto community waits for further updates, the importance of cybersecurity measures is more significant than ever. As suggested by a user, "It might be time to move all funds to cold storage; things are getting dicey,โ€ reflecting a sentiment of caution amid growing unease.