The facts

  1. Polymarket's public statement said it had identified and fixed an international-platform issue involving a compromised third-party provider, referred the matter to law enforcement and would make affected users whole. [1]

  2. CNBC reported that international trading resumed at 15:00 EDT after the temporary halt. AP also reported that trading had resumed after a roughly hour-long pause. [2][3]

  3. CNBC identified the provider as DebugBear, citing a person familiar with the matter. DebugBear separately disclosed a security incident affecting users of its real-user monitoring service; that disclosure alone does not establish the full attack chain. [2][4]

  4. AP and CNBC reported that the US platform was not affected. The sources did not establish a final total of losses or affected customers. [2][3]

Still unconfirmed

  • The final loss, number of affected customers, complete intrusion method and completion of promised reimbursements remain unestablished.

Sources

References support the numbered facts above. Source checks: 29 Oct 2026, 23:12 UTC.

  1. International-platform security incident statement

    Polymarket Traders · Primary source · 29 Oct 2026

    The core statement was read through X's intentionally public oEmbed response. The embed truncated the subsequent cautionary passage; no unsupported detail is inferred from that passage.

  2. Polymarket reports outage on international exchange, halts trading

    CNBC · Reporting · 29 Oct 2026

    Actual report read. CNBC discloses a commercial relationship with competing prediction market Kalshi. Theft, scope and the provider attribution are distinguished from independently completed forensic findings.

  3. Polymarket paused international trading after a third-party security issue

    The Associated Press via ClickOrlando · Reporting · 29 Oct 2026

    Kaitlyn Huamani's actual report read. AP is independently owned from CNBC, Polymarket and DebugBear.

  4. Security incident affecting real-user monitoring

    DebugBear · Primary source · 29 Oct 2026

    Full short public statement read through the public oEmbed response. No external scripts or instructions were executed.

Report a factual error