Supply Chain Attack on Polymarket Costs Traders .7 Million via Hijacked Third-Party Script
By ICCSO News Desk
2026-11-02T11:53:40.775Z
A supply chain attack targeting prediction market platform Polymarket resulted in the theft of approximately 2.7 million US dollars from hundreds of trader accounts on 29 October. Malicious code, injected into a third-party page-speed script the platform loaded from an external provider called DebugBear, silently liquidated signed-in users' positions and redirected their funds to the attackers. Polymarket has confirmed it is refunding around 2.7 million dollars to 726 affected wallets, with blockchain records indicating that approximately 2.64 million dollars in cryptocurrency reached the attackers. The incident is a sharp reminder of the risks posed by third-party script dependencies, a threat vector that remains underestimated across both the financial technology sector and wider industry.
What happened and when On 29 October, users of Polymarket — a decentralised prediction market platform that allows participants to trade on the outcomes of real-world events — found that their signed-in accounts had been compromised. Malicious code executed within their browsers, automatically selling open positions and transferring the resulting funds to wallets controlled by the attackers. The incident was not caused by a direct breach of Polymarket's own infrastructure, but by the compromise of a third-party script the platform loaded at runtime. The vector traced back to DebugBear, an external page-performance monitoring service whose script Polymarket embedded on its site. Attackers had apparently replaced or tampered with that script, turning it into a vehicle for malicious code that ran with full access to the browser sessions of authenticated users. Who is affected Polymarket has confirmed that 726 wallets were compromised during the incident. The platform is in the process of refunding approximately 2.7 million US dollars to those affected. Blockchain data corroborates the scale of the theft, with around 2.64 million dollars in cryptocurrency confirmed as having reached attacker-controlled addresses. Polymarket operates globally and is predominantly used by retail cryptocurrency traders and prediction market participants. While the platform is not headquartered in the United Kingdom, the incident carries direct relevance for UK-based users of the service, as well as for any organisation — financial or otherwise — that embeds third-party scripts into customer-facing web applications. The technical detail This incident is a textbook example of a software supply chain attack delivered through a browser-side dependency. Modern web applications routinely load scripts from external providers to handle functions such as analytics, performance monitoring, chat widgets, payment processing, and advertising. Each of these external scripts typically runs in the same browser context as the host application, meaning it can read and manipulate page content, access session data, and interact with any in-page functionality — including, in the case of a financial platform, the ability to initiate transactions on behalf of a signed-in user. In this case, the DebugBear script was a trusted dependency used for page-speed measurement. Once attackers succeeded in modifying the content delivered by that script — whether by compromising DebugBear's own systems, intercepting the delivery pipeline, or another means not yet publicly confirmed — every Polymarket user who loaded the page while authenticated became a potential victim. The malicious code acted silently, selling their open trading positions and routing the proceeds to attacker wallets without requiring any further action from the user. No specific Common Vulnerabilities and Exposures identifiers have been cited in reporting at this stage. The precise method by which the DebugBear script was tampered with has not been publicly disclosed. Timeline of events Based on currently available reporting, the malicious script was active on 29 October, the date on which the unauthorised transactions occurred. Polymarket subsequently identified the scope of the incident, traced the cause to the compromised third-party dependency, and announced a refund programme covering all 726 affected wallets. The timeline of discovery, containment, and remediation has not been detailed in full in public reporting to date. Attribution and threat-actor context No attribution to a specific threat actor or group has been made public at this stage. The attack methodology — targeting a trusted third-party supplier rather than the primary platform directly — is consistent with a well-established pattern in financially motivated cybercrime. Cryptocurrency platforms and decentralised finance services have been frequent targets for this class of attack given the speed and irreversibility with which digital assets can be moved once accessed. The use of a page-performance or analytics script as the infection vector is also consistent with prior incidents in which attackers have targeted less-scrutinised parts of the web supply chain. High-profile examples from recent years include the compromise of scripts used by major e-commerce and travel platforms, where attackers skimmed payment card data rather than cryptocurrency — but the underlying technique is functionally similar. What Polymarket is doing Polymarket has committed to refunding the approximately 2.7 million dollars lost by affected users. Beyond the financial remediation, the platform has not detailed its ongoing security measures or its remediation steps in relation to the compromised dependency. Users of the platform should verify whether they were among the 726 wallets affected and monitor communications from Polymarket regarding the refund process. Regulatory and compliance implications for UK organisations While Polymarket itself is not subject to UK financial regulation, the incident raises important questions for UK-regulated organisations that operate web applications with third-party script dependencies — which is effectively every financial services firm, e-commerce operator, and digital service provider. Under UK GDPR and the Data Protection Act 2018, organisations are responsible for the processing activities carried out on their behalf by third parties. A compromised third-party script that exfiltrates data or enables unauthorised access to user accounts could constitute a personal data breach requiring notification to the Information Commissioner's Office within 72 hours of becoming aware, where the breach poses a risk to individuals. For firms in scope of the Network and Information Systems (NIS) Regulations, and for financial services entities preparing for alignment with DORA — the EU's Digital Operational Resilience Act, which has cross-border implications for many UK firms with European operations — third-party ICT risk management is an explicit compliance obligation. DORA in particular requires firms to maintain registers of third-party dependencies, conduct risk assessments, and establish contractual protections covering security standards and incident notification. The NCSC has published guidance on supply chain security and software skimming attacks that is directly relevant here. UK organisations should treat this incident as a prompt to revisit their own third-party script inventories and controls. Mitigation and the state of current defences For organisations seeking to reduce exposure to this class of attack, several technical controls are available and should be considered as baseline practice for any customer-facing web application. Subresource Integrity (SRI) is a browser security feature that allows a web page to specify a cryptographic hash for each external script it loads. If the script's content has been modified — as occurred in this incident — the browser will refuse to execute it. SRI is not universally implemented, particularly where external scripts are updated frequently, but it represents one of the most direct mitigations for this threat. Content Security Policy (CSP) headers can restrict which external domains a page is permitted to load scripts from and can prevent inline script execution, reducing the attack surface available to an injected payload. Real-time monitoring of third-party script behaviour, supplier security assessments, and the principle of minimising the number of external dependencies loaded on sensitive application pages are all practices that materially reduce risk. Polymarket's decision to refund affected users reflects the reputational and financial stakes for any platform that suffers this kind of breach — and underscores why preventative controls are considerably less costly than remediation after the fact.