Polkadot’s central Treasury suffered a financial loss of $1.38 million after an attacker successfully exploited a security vulnerability that developers had identified and fixed months before the network’s new decentralized stablecoin officially launched.
According to a comprehensive incident report published by Parity Technologies on November 2, the core security flaw was discovered and corrected in the blockchain infrastructure firm’s codebase as early as June. However, due to a breakdown in deployment tracking and risk assessment, the crucial patch never reached the affected production systems before a series of malicious attacks unfolded between October 24 and October 26.
The security breach exposed critical vulnerabilities surrounding the rollout of dotUSD, Polkadot’s newly introduced decentralized stablecoin. The asset made its debut in October operating under the governance of the network’s decentralized autonomous organization (DAO), distinguishing itself from traditional stablecoins issued by centralized private companies by relying instead on DOT holders to govern operational decisions through the network’s OpenGov system.
Despite its decentralized architecture, the architectural interplay between the codebase and the new asset class proved fatal. Parity initially classified the bug as a medium-severity issue during its initial discovery in June. According to the developer’s post-mortem review, this lowered classification stemmed from an assessment failure that did not adequately consider how the underlying software flaw might interact with dotUSD, which at the time had not yet been integrated or launched on the mainnet. Following the October exploitation and its subsequent financial fallout, Parity developers formally upgraded the vulnerability status to critical.
The incident was further complicated by an untimely public disclosure days before the attack. On October 20, the security researcher who originally discovered and reported the vulnerability posted a public forum comment referencing the specific code fix. Although Parity quickly intervened and the researcher removed the comment after being notified that it violated the company’s bug bounty rules, developers now believe that the brief public exposure may have provided malicious actors with sufficient technical clues to identify and target the unpatched vulnerability across production systems.
The attacker executed the breach by cleverly manipulating the Polkadot Asset Hub’s cross-chain messaging system, known as XCM. By exploiting the flaw, the perpetrator artificially reduced the recorded supply of dotUSD without actually removing any actual tokens from users’ individual accounts. This discrepancy created an immediate imbalance that severely distorted prices within the network’s native DOT/dotUSD liquidity pool. Consequently, traders were able to exchange dotUSD for DOT at heavily artificial and exploitative rates. Because the Polkadot Treasury served as the pool’s sole liquidity provider, it absorbed the entirety of the approximately $1.381 million in losses generated by the price distortion.
Parity emphasized throughout its disclosure that everyday users did not lose any funds during the exploit and that dotUSD remained fully backed by USDT. Nonetheless, the infrastructure firm noted that it has remained impossible to definitively establish whether the individual who originally exploited the vulnerability also reaped the financial profits from the subsequent arbitrage trading activity.
Hacker Bypassed Emergency Shutdown Before Polkadot Deployed Security Fix
The situation escalated significantly when the attacker successfully circumvented an emergency containment measure specifically deployed to halt the exploit in real time.
After network monitors detected suspicious activity on October 24, Snowfork—the core development team behind the Snowbridge network—halted its consensus relayers. This emergency action was intended to temporarily block further malicious transactions from reaching the Polkadot ecosystem through Snowbridge. However, because the Snowbridge architecture permits independent participants to operate their own relayers, Snowfork’s intervention only successfully interrupted its own infrastructure rather than completely blocking all network access.
Taking advantage of this decentralized design, the attacker operated an independent relayer on October 26, successfully resuming the exploit approximately six hours before developers were able to officially deploy the comprehensive security upgrade through OpenGov.
Parity ultimately neutralized the threat by pushing runtime upgrade 2.5.1 on October 26, which effectively closed the cross-chain vulnerability and allowed developers to rescue the remaining liquidity from the compromised trading pool. A second runtime upgrade followed shortly after on October 30, correcting the recorded supply of dotUSD without altering individual user account balances while simultaneously resolving a separate technical issue that had temporarily disrupted normal operations on Snowbridge. The recovered dotUSD was subsequently returned to the Treasury, though the financial losses incurred from the earlier artificial trading activity could not be reversed.
In the wake of the incident, Parity acknowledged that its existing internal security processes failed to adequately account for the evolving risks introduced by the deployment of new network functionality. The company announced plans to strengthen its vulnerability assessments, improve pre-deployment checks, and significantly expand continuous monitoring protocols for unusual asset issuance across the ecosystem.
As part of its long-term remediation efforts, Parity is currently refining an automated AI-based security framework designed to identify potentially exploitable code changes much earlier in the development lifecycle. The firm is also systematically reassessing previously cataloged vulnerabilities to identify any hidden risks that might be introduced by the ongoing integration of dotUSD and other network features.
