Polymarket Pauses Trading After Third-Party Provider Compromise

Polymarket has restricted trading and paused relayer actions following reports of unauthorized fund withdrawals from user accounts. The prediction market platform confirmed that one of its third-party providers was compromised, leading to a major outage of its trading API and the implementation of cancel-only mode.

Researchers identified a malicious script hosted on DebugBear that targeted logged-in users to sell positions and transfer assets. A suspected attacker wallet associated with the incident currently holds approximately $2.65 million in POL tokens after converting USDC.e through a cross-chain swapping service.

Key facts

  • Polymarket placed its exchange in cancel-only mode and paused relayer actions due to the security incident.
  • A wallet flagged as the suspected attacker’s holds about $2.65 million in POL, according to Arkham data.
  • Hudson Rock researchers found a DebugBear-hosted script containing wallet-draining code that hard-codes the attacker’s address.
  • Polymarket stated it has referred the matter to relevant law enforcement and promised to make impacted users whole.
  • The incident is linked to a compromised third-party provider rather than a direct breach of Polymarket’s core infrastructure.

Why it matters

The platform explicitly committed to refunding any users who were impacted by the unauthorized withdrawals, ensuring financial restitution for those affected by the compromised third-party provider.

Sources

Safety First: Please revoke all active wallet approvals immediately via Revoke.cash or similar tools. Do not interact with any links from the compromised DebugBear script.

Timeline & Evidence:

  1. Compromise: A third-party analytics provider, DebugBear, was breached.
  2. Exfiltration: Malicious code injected into their scripts targeted logged-in users on Polymarket.
  3. Impact: Unauthorized trades executed to sell positions and transfer assets to a specific attacker wallet.
  4. Response: Polymarket entered cancel-only mode and paused relayer actions to halt further losses.

Underline: The core failure lies in the supply chain trust model.

This incident highlights how blockquote + highlight even reputable platforms are vulnerable when relying on external scripts. The attacker did not hack Polymarket directly but exploited a trusted vendor. Users must assume that any integrated third-party service is a potential attack vector. Always verify contract interactions before signing transactions.

Preserve screenshots of any unauthorized activity for reporting purposes.

Regarding “Polymarket Pauses Trading After Third-Party Provider Compromise”, what evidence would clearly distinguish changed behavior from activity merely shifting elsewhere over time?