A sophisticated supply-chain attack struck the popular decentralized prediction market Polymarket on October 29, resulting in the unauthorized liquidation of trading positions and the swift redirection of funds to malicious actors. The security breach, which unfolded rapidly over the course of an hour, exploited a vulnerability in a third-party performance monitoring script used by the platform, prompting an immediate emergency response, comprehensive platform shutdowns, and a commitment by Polymarket to issue millions of dollars in refunds to affected users.
According to preliminary findings and disclosures from cybersecurity researchers, the incident began when malicious code was injected into a page-speed script that Polymarket loaded dynamically from an external vendor. Specifically, the compromised script originated from DebugBear, a real user monitoring (RUM) service utilized by organizations to measure web page loading speeds for visitors. Rather than a direct breach of Polymarket’s core infrastructure or internal servers, the vector of attack leveraged a domain registrar compromise that affected DebugBear’s DNS records, allowing unauthorized entities to substitute legitimate performance monitoring files with malicious payloads targeting specific customer implementations.
Blockchain records analyzed by researchers indicate that the exploit began taking a heavy financial toll at approximately 17:10 UTC on October 29. Within a span of less than sixty minutes, crypto assets valued at millions of dollars were funneled into a designated hacker-controlled wallet. Cybersecurity firm Hudson Rock, whose analysts downloaded and examined the malicious file shortly after the attack went live, confirmed that the script was strategically crafted to interact with active browser sessions of signed-in Polymarket traders.
How the Malicious Script Executed the Drain
Unlike traditional phishing campaigns that attempt to trick users into revealing private keys or seed phrases, the Polymarket exploit operated silently within the browser environment of authenticated users. Researchers analyzing the static code discovered that the malicious script bypassed the need for direct access to private credentials by reusing the active session permissions already established by a signed-in trader on an open Polymarket web page.

The script systematically scanned the browser DOM to read account details retained locally by Polymarket, including specific trading API keys. However, because API keys alone are insufficient to execute trades or transfer assets on the platform—transactions inherently requiring a valid wallet signature—the script executed a more complex operational bypass. It located the core user interface components responsible for order placement and transaction approvals within the site’s architecture.
Depending on the authentication method employed by the individual trader, the script deployed one of two distinct pathways to siphon funds. For accounts authenticated directly through external crypto wallets, the script initiated commands to transfer user positions straight to the attacker’s wallet address. For users who logged in via email-based onboarding flows, the script programmatically sold off active trading positions at heavily depressed, unfavorable market prices before routing the resulting capital out of the ecosystem.
Throughout this process, the script leveraged the account’s legitimate internal signer to authorize requests and pushed them directly through Polymarket’s native transaction relayer. Cybersecurity analysts noted that while the code commanded the signer to execute requests, the exact nature of user prompts during the session depended heavily on individual wallet provider configurations, session rules, and security boundaries.
Blockchain tracking conducted by researchers at Ohey revealed the intense velocity of the assault. The targeted wallet address recorded its initial inbound transfer at 17:10 UTC and its final accumulation at 18:02 UTC. Across this brief window, the address amassed approximately 28.6 million POL tokens alongside various trading positions harvested from 33 distinct user wallets. Calculations based on market pricing from DefiLlama pegged the value of the accumulated POL tokens alone at approximately $2.64 million at 18:19 UTC. Shortly after gathering the illicit funds, transaction history logs show the receiving address systematically dispersed the entire 28.6 million POL balance across three separate external cryptocurrency addresses between 18:28 and 18:38 UTC.

Polymarket’s Incident Response and Comprehensive Refund Program
Polymarket’s operational and security teams identified abnormal activity within user accounts swiftly, issuing their first public status advisory regarding unauthorized transactions at 17:38 UTC. Recognizing the severity of the frontend compromise, the exchange swiftly escalated its defensive posture. By 18:05 UTC, platform operators transitioned the exchange into a strict cancel-only mode, temporarily halting all trading activity and freezing relayer actions to contain the spread of the exploit.
Company representatives stated that the malicious script was excised from the platform within an hour of detection. In tandem with removing the rogue code, Polymarket engineers flushed all server and content delivery network caches, terminated all active user login sessions globally, and kept trading disabled until thorough security sweeps confirmed the environment was entirely sanitized. The company formally escalated the matter to external law enforcement agencies for formal investigation.
Demonstrating significant financial accountability in the wake of the breach, Polymarket announced a comprehensive reimbursement initiative designed to make every impacted trader whole. By October 30, the platform had successfully refunded 689 out of 726 directly affected wallets in full, with the remaining accounts undergoing standard verification before receiving payouts. Furthermore, Polymarket expanded its compensation scope to encompass approximately 5,500 additional wallets that suffered financial setbacks due to positions being liquidated during the emergency trading freeze or affected by forced position closures.
In total, Polymarket committed to returning approximately $3.9 million to the trader community. Platform administrators emphasized that affected users were not required to navigate cumbersome claim-filing procedures for standard reimbursements, though an official inquiry form was established via the company’s status page for individuals seeking to review specific payment discrepancies or verify missing allocations.

Industry Ramifications and Preventative Measures
The incident has underscored persistent supply-chain vulnerabilities inherent in modern web applications that rely heavily on third-party JavaScript libraries, analytics plugins, and external content delivery networks. DebugBear advised all clients utilizing its real user monitoring services to temporarily decouple and remove embed codes from their respective web properties while infrastructure reviews continued. Technical evaluations confirmed that the specific endpoint utilized to serve the compromised script, cdn.debugbear[.]com, was stripped of active DNS records in the aftermath of the discovery.
In response to the breach, Polymarket outlined plans to reinforce its frontend security architecture. Moving forward, the platform intends to implement rigorous defensive controls for all third-party integrations, including stricter Content Security Policies (CSP), cryptographic version pinning to prevent unauthorized file substitutions, and advanced sandboxing techniques to isolate external scripts from sensitive browser sessions and DOM elements.
Cybersecurity analysts and researchers continue to urge web application developers to audit external dependencies rigorously and monitor dynamic script execution environments closely. For cryptocurrency traders interacting with decentralized applications, security experts reiterate the importance of exercising heightened vigilance, verifying active transaction prompts, and instantly revoking session permissions or disconnecting wallets upon encountering unexpected application behavior.
