{"id":3043,"date":"2026-10-31T07:03:49","date_gmt":"2026-10-31T07:03:49","guid":{"rendered":"https:\/\/smartcryptosecurity.com\/?p=3043"},"modified":"2026-10-31T07:03:49","modified_gmt":"2026-10-31T07:03:49","slug":"polymarket-halts-trading-on-international-platform-following-third-party-security-breach-and-unauthorized-withdrawals","status":"publish","type":"post","link":"https:\/\/smartcryptosecurity.com\/?p=3043","title":{"rendered":"Polymarket Halts Trading on International Platform Following Third-Party Security Breach and Unauthorized Withdrawals"},"content":{"rendered":"<p>Polymarket, one of the world&#8217;s leading prediction markets, was forced to temporarily halt trading on its international platform on October 29 after users began reporting unauthorized withdrawals and suspicious account activity. The sudden disruption underscored the persistent vulnerabilities associated with third-party software dependencies in the decentralized finance and cryptocurrency sectors, as security researchers quickly traced the root cause of the incident to a compromised website performance monitoring service.<\/p>\n<p>According to the official status page managed by the prediction market, the exchange was initially switched to a restrictive cancel-only mode shortly after the suspicious activity was detected. Simultaneously, platform operators suspended relayer actions to prevent further unauthorized transactions from being processed on the blockchain. <\/p>\n<p>Company representatives moved quickly to address the crisis publicly and reassure panicked users. In a statement posted to social media, Polymarket confirmed the nature of the disruption, stating that they had identified and fixed an issue impacting their international platform at Polymarket.com. The company explained that one of their third-party providers had been compromised and noted that the breach had been referred to relevant law enforcement agencies for a formal investigation. Furthermore, Polymarket made a definitive public pledge that anyone who had been impacted by the security incident would be made whole, promising full reimbursement to all affected traders.<\/p>\n<p>Trading on the international platform resumed approximately an hour after the initial halt once mitigation measures were fully deployed. Despite the swift resumption of normal operations, the company initially refrained from naming the specific vendor involved or disclosing an exact tally of total financial losses. However, the identity of the third-party provider quickly came to light through independent cybersecurity research.<\/p>\n<p>Investigators and threat intelligence researchers soon linked the malicious activity to malicious code that was being served directly from DebugBear, a United Kingdom-based website performance monitoring firm widely utilized by web platforms to track user metrics. Throughout the incident, Polymarket\u2019s separate United States-based platform reportedly remained entirely unaffected by the compromise.<\/p>\n<p>DebugBear quickly acknowledged the unfolding crisis, confirming via social media that it had been impacted by an ongoing security incident. The monitoring firm strongly urged users of its real user monitoring product to immediately remove its tracking snippet from their respective websites as a precautionary measure. DebugBear also announced that it had brought in specialist incident responders to contain the breach, audit its infrastructure, and determine how its systems were manipulated to serve malicious payloads.<\/p>\n<p>Technical analysis conducted by cybersecurity firm Hudson Rock provided deeper insight into how the exploit was executed. Hudson Rock researchers managed to obtain a copy of the malicious JavaScript file from a specific DebugBear address that had been utilized directly by Polymarket. According to their technical breakdown, the injected script was meticulously designed to hunt for a logged-in user\u2019s active trading tools and portfolio details. <\/p>\n<p>Depending on the specific account type and authentication status, the malicious script attempted one of two aggressive actions. In some instances, it tried to sell existing user positions and seamlessly move the resulting proceeds to an attacker-controlled destination. In other cases, it bypassed the liquidation step entirely, attempting to send valuable position tokens directly to an address established by the hackers.<\/p>\n<p>Despite the invasive nature of the script, security analysts noted that it operated through existing authentication sessions rather than harvesting foundational master credentials. Hudson Rock reported that the examined sample read credential-related material, but their thorough review did not identify a routine that exported a credential map, a raw password, a user seed phrase, or a private key to an external reporting endpoint. Instead, the central approach of the attack relied entirely on abusing the authority and permissions already available within the actively authenticated application session of the victim.<\/p>\n<p>Further corroborating the timeline of the attack, Hudson Rock researchers spotted a Polymarket production build, timestamped at 17:59 UTC, which featured an internal change note explicitly detailing the removal of the compromised DebugBear script. <\/p>\n<p>Estimates regarding the total financial impact of the breach varied across different blockchain intelligence and security organizations. A forensic screenshot reviewed by Hudson Rock revealed approximately $2.19 million sitting at the script\u2019s hard-coded fallback address, though the firm cautioned that this figure did not represent a verified or final tally of stolen funds.<\/p>\n<p>Meanwhile, blockchain security firm GoPlus independently attributed the attack to a severe supply chain compromise affecting DebugBear\u2019s real user monitoring script. GoPlus put total losses at roughly $2.71 million based on comprehensive on-chain analysis. Their investigation indicated that the primary attack path wound its way through approximately 710 deposit wallets and 731 distinct addresses, though security experts emphasized that the total count of interacting addresses does not directly equate to the precise number of individual human victims.<\/p>\n<p>Additional data compiled from Arkham Intelligence pointed to a suspected attacker wallet holding approximately $2.65 million in digital assets. This specific blockchain address matched the exact fallback recipient address hardcoded directly into the malicious JavaScript script. <\/p>\n<p>Despite the breadth of the forensic data, Hudson Rock noted that researchers had not yet determined the precise vector used to tamper with the script on DebugBear&#8217;s infrastructure, nor had they established the exact number of end-users whose accounts were successfully compromised. Crucially, the firm&#8217;s preliminary findings did not indicate that other corporate customers utilizing DebugBear services were similarly targeted or exploited during the incident.<\/p>\n<p>The Polymarket security breach coincided with a turbulent period for the broader digital asset ecosystem. The attack occurred on the exact same day that cryptocurrency exchange Binance was hit by a massive security breach resulting in an estimated $6 billion loss, an incident that prominent blockchain intelligence firms have formally attributed to state-sponsored actors linked to North Korea. <\/p>\n<p>For Polymarket specifically, the October 29 incident marked the second major public security scare of the year. In June, the prediction market disclosed another third-party compromise that successfully injected a malicious script into its frontend user interface, resulting in reported losses of approximately $3 million at the time. As decentralized platforms and prediction markets continue to rely heavily on third-party integrations and external web scripts, the latest breach serves as a stark reminder of the fragile nature of software supply chains in modern web applications.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Polymarket, one of the world&#8217;s leading prediction markets, was forced to temporarily halt trading on&#8230;<\/p>\n","protected":false},"author":9,"featured_media":3042,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[313],"tags":[323,165,363,321,2577,320,908,1243,468,2576,5,918,322,86,1342,878],"class_list":["post-3043","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-incident-response-forensics","tag-blockchain-analysis","tag-breach","tag-following","tag-forensics","tag-halts","tag-incident-response","tag-international","tag-party","tag-platform","tag-polymarket","tag-security","tag-third","tag-tracking","tag-trading","tag-unauthorized","tag-withdrawals"],"_links":{"self":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts\/3043","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3043"}],"version-history":[{"count":0,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts\/3043\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/media\/3042"}],"wp:attachment":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3043"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3043"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3043"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}