Pirate Chain confirmed an exploit involving a vulnerability that resulted in approximately 39800000 tokens ARRR being created without authorization; dPoW temporarily suspended notarization
BIBIBI
AT A GLANCE
Pirate Chain said a transaction verification vulnerability resulted in approximately 39800000 tokens ARRR being created without authorization.
Article
Pirate Chain confirmed that it was attacked recently, with the token supply increasing by approximately 20%BlockBeats reported that October 16，Pirate Chain released an update on its investigation into the exploit.October 14，Pirate Chain found a transaction verification vulnerability in the source code, which resulted in approximately 39800000 tokens being created without authorization,ARRR increasing the total token supply by approximately 20%. These newly generated tokens were then transferred to the Sapling privacy pool. The NonKYC platform subsequently detected suspicious deposits, restricted the relevant accounts, and blocked withdrawals. The exploit involved the failure of two verification steps: first, bypassing the issuance check, and second, incorrectly parsing the output script.
As a voluntary precautionary measure, dPoW (delayed proof-of-work) operators reached a consensus to temporarily suspend notarization services. At the same time, the team requested that exchanges and mining pools voluntarily suspend related operations while a recovery plan is being developed. Currently, the Pirate Chain network remains operational.Pirate Chain team is investigating the incident and working with other communities to develop a solution.
Original link https://m.theblockbeats.info/flash/372120
Key points
01
October 14，Pirate Chain A transaction verification vulnerability was found in the source code.
02
The vulnerability resulted in approximately 39800000 tokens ARRR being created without authorization, increasing the total token supply by approximately 20%。
03
The newly generated tokens were transferred to the Sapling privacy pool.
04
The NonKYC platform detected suspicious deposits, restricted the relevant accounts, and blocked withdrawals.
05
The exploit involved bypassing the issuance check and incorrectly parsing the output script in two verification steps.
Pirate Chain The network remains operational, and the team is investigating the incident and developing a solution.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
The attacker exploited a transaction verification vulnerability to create a large number of new ARRR tokens. After some tokens entered the privacy pool, the platform restricted the relevant accounts and withdrawals; notarization services were also temporarily suspended.
Why it matters to readers
The supply increased by approximately 20%which may affect token scarcity; restrictions on accounts and withdrawals, along with the suspension of notarization services, indicate that related operations have been affected.
This indicates a security issue in the project's transaction verification mechanism. Users should monitor the official fix, platform restrictions, and the restoration of network services.
Risks and unknowns
The evidence does not state whether the vulnerability has been fixed.
The evidence does not state how the newly generated tokens will be handled.
The evidence does not state when exchanges, mining pools, and notarization services will resume.
The evidence does not provide on-chain verification results or information about user losses.
Related Developments
Loading event timeline…
Related concepts
Transaction-validation vulnerability
This term is not in the glossary yet. Browse related concepts in the glossary.
