Pirate Chain exploit mints 39.8 million ARRR tokens without authorization

A source code flaw in the privacy-focused Pirate Chain network enabled the unauthorized minting of approximately 39.8 million ARRR tokens on October 14, 2026, representing roughly 20% of its total token supply. Traced to two validation failures from the recent Ironwood upgrade, the illicit funds were moved into the Sapling shielded pool. In response, developers proposed a blockchain rollback to 20:00 UTC on October 14, while exchange NonKYC froze affected deposits.

Scope of unauthorized token minting

• ▪Pirate Chain targets a maximum total supply ceiling of 200 million ARRR tokens
• ▪The unauthorized minting of 39.8 million ARRR tokens represented roughly 20% of the total Pirate Chain token supply at the time of the October 14, 2026 exploit
• ▪A source code flaw in the Pirate Chain privacy network allowed an unauthorized user to mint approximately 39.8 million ARRR tokens on October 14, 2026

Privacy shielding complicates token tracing

• ▪Pirate Chain enforces mandatory zk-SNARKs privacy shielding across 100% of its network transactions
• ▪Following the unauthorized minting of 39.8 million ARRR tokens on October 14, 2026, the illicit tokens were rapidly moved into Pirate Chain's Sapling shielded pool
• ▪Pirate Chain developers acknowledged that the cryptographically hidden nature of Sapling pool transactions complicates efforts to trace where the 39.8 million unauthorized ARRR tokens went

Developer mitigation and network status

• ▪The Pirate Chain network remained operational while developers worked on recovery, instructed wallet users not to move funds, and requested exchanges and mining pools voluntarily pause operations following the October 14, 2026 exploit that minted 39.8 million ARRR tokens
• ▪The Pirate Chain development team proposed a blockchain rollback to revert the network to its state as of 20:00 UTC on October 14, 2026, discarding all subsequent blocks