TL;DR A compromised third-party web monitoring tool allowed attackers to siphon an estimated $2.65 million from user wallets before trading was temporarily paused. Key facts: $2.65 million (Estimated crypto siphoned from user wallets); 1 hour (Approximate length of international trading suspension).
$2.65 million
Estimated crypto siphoned from user wallets 12
1 hour
Approximate length of international trading suspension 1
DebugBear
Third-party performance tool compromised in the breach 12
$21 billion
Polymarket valuation following September 2026 investment 1
Contents
  1. Incident Timeline and Operational Status
  2. Attack Vector and Technical Execution
  3. Financial Impact, History, and Investigations
  4. What is not yet established
  5. Frequently asked questions
  6. Sources

Incident Timeline and Operational Status

On October 29, 2026, prediction market platform Polymarket temporarily suspended trading activity across its primary international domain, Polymarket.com, following reports of unauthorized account drains 12. The platform remained inactive for approximately one hour while engineers evaluated an unauthorized intrusion linked to an external software component 1. During the disruption, internal system monitors indicated that the trading application programming interface experienced a severe outage, forcing the exchange into a cancel-only operational mode 2. This setting permitted market participants to retract active orders but blocked the submission of new orders, while automated relayer services responsible for broadcasting signed user transactions to the blockchain were entirely suspended 2. According to platform representatives, the security compromise did not impact the platform's dedicated U.S.-based operational infrastructure 1.

Initial alerts emerged when traders using the platform reported unexpected asset withdrawals and automated liquidations taking place without user authorization 2. In response to growing concern across public discussion channels, Polymarket confirmed via its official account on X that an external third-party vendor had been compromised 12. The organization publicly committed to restoring missing funds, posting that "anyone who has been impacted will be made whole" 12. A subsequent statement reinforced this stance, with the platform stating, "We'll make this right and are fully reimbursing all affected traders" 1. Management confirmed that the immediate vulnerability on Polymarket.com had been localized and patched before restoring normal service 12.

Attack Vector and Technical Execution

Technical analysis by external cybersecurity researchers highlighted a supply chain vector involving DebugBear, a web analytics and site performance tracking service integrated into Polymarket's web interface 12. According to an anonymous source familiar with the matter, malicious actors gained access to platform infrastructure through DebugBear's external software pipeline 1. DebugBear publicly acknowledged an ongoing security problem on October 29, 2026, around 2:00 p.m. ET 1. Analysis by cybersecurity firm Hudson Rock revealed that a malicious script delivered through DebugBear specifically targeted active user sessions on the frontend 2. The injected code inspected active client logins, executed automated position sales, and transferred the resulting funds to an attacker-controlled external wallet 2.

Hudson Rock reported that the underlying script contained a hard-coded fallback address designated to receive stolen assets 2. Inspection of Polymarket's production source code later confirmed that engineering teams manually removed the compromised script dependency to neutralize the exploit vector 2. Blockchain records tracked by data analytics platform Arkham identified the primary wallet associated with the intruder as 0x3F99139F1C5854bb628c2e576Aaf638e99dFfc18 2. Transaction histories indicate that the attacker received bridged USDC.e tokens from compromised accounts and immediately routed them through Relay, a cross-chain swapping protocol, converting the holdings into Polygon's native POL token 2.

Financial Impact, History, and Investigations

Data compiled by Arkham indicated that the attacker successfully siphoned approximately $2.65 million in digital assets from user wallets during the brief exploit window 12. Although the identified wallet accumulated significant holdings in POL before activity ceased, a representative for Polymarket declined to verify the exact monetary damage or discuss specific operational mechanics of the breach 1. This security incident marks the third notable compromise involving Polymarket during 2026 2. Earlier in May 2026, a private key compromise resulted in the loss of roughly $700,000 from an internal wallet used for system top-ups 2. In June 2026, a separate third-party vendor breach allowed attackers to inject frontend code and steal nearly $3 million from fewer than 15 accounts, an incident that also resulted in full user reimbursements 2.

Polymarket stated that initial forensic indicators trace the origin of the attack to the United Kingdom, prompting the firm to refer the breach to British law enforcement agencies 1. The breach occurred amidst significant operational growth and regulatory scrutiny for the venue 1. In September 2026, Polymarket achieved a valuation of $21 billion after securing a $1 billion funding round led by Donald Trump Jr. 1. The exchange routinely handles approximately $200 million in daily transaction volume 1. Concurrently, the platform has been conducting internal compliance reviews regarding potential market manipulation 1. Shana Bautista, head of global intelligence and investigations at Polymarket, confirmed that the platform is investigating dozens of suspicious transactions related to U.S. midterm elections, alongside reported anomalies surrounding Israel's national elections 1.

What is not yet established

  • The precise number of individual user accounts compromised during the incident
  • How malicious code was originally injected into DebugBear's deployment pipeline
  • The exact monetary loss figure officially verified by Polymarket internal auditing
  • The specific identity or organization behind the attacker's wallet address

Frequently asked questions

How did the security breach on Polymarket occur?

Attackers exploited a compromise at DebugBear, a third-party performance analytics vendor integrated into Polymarket's website 12. The vendor's code delivered a malicious script that hijacked active client sessions, sold user holdings, and transferred funds to an external wallet 2.

Will traders who lost funds be compensated?

Polymarket publicly stated that all affected users will be fully reimbursed and made whole 12. The company previously provided full compensation to affected users following a similar vendor security breach in June 2026 2.

Was the U.S. platform affected by the trading halt?

No, company representatives confirmed that the disruption was restricted to its international site, Polymarket.com, and did not impact U.S. operations 1.

Sources

  1. Hacker News — Polymarket 1h halt after vendor compromise; affected users will be 'made whole' (2026-10-30) https://www.nbcnews.com/business/consumer/polymarket-trading-halt-hack-wallets-rcna606405
  2. Decrypt — Polymarket Pauses Trading as Prediction Market Investigates Security Incident (2026-10-29) https://decrypt.co/382185/polymarket-pauses-trading-prediction-market-security-incident

Revision history

v1.0
31 October 2026
Published