Pirate x Pirate Hack

TOTAL LOST $78K
Low Access Control

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #1578 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

Pirate X staking contract was attacked resulting in the loss of 9,681,000 PXP tokens, which were later dumped into the market, netting the attacker a profit of about 212 BNB.

The attack on Pirate X's staking contract is believed to have been due to the leakage of the private key, as the attacker used a valid signed message to launch the attack. Users who deposited their PXP tokens into the contract had their tokens transferred to an EOA account (0x3b74a9cb…0067b7). The contract would then call transferFrom to transfer the tokens back to the user upon withdrawal.

The attacker provided a valid sign from the external signer (0x7435e0e4…eb176d) and withdrew 9,681,000 PXP tokens.

The staking contract: 0x6912B194…92DA54

Attacker: 0x3b74a9cb…0067b7

External signer: 0x7435e0e4…eb176d.

Incident Report

Protocol / Project Pirate x Pirate
Date of Incident
Attack Technique Access Control
Classification NFT
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Access control
Affected Token PXP
Official Website piratexpirate.io/
Protocol Twitter/X @PXPNFTsGame
Team Anonymous
Source Code Unverified

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Pirate x Pirate's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Access Control audit checklist and test coverage

If you're auditing a protocol with similar architecture to Pirate x Pirate, these are the critical security checks that could have prevented this incident (March 2022).

  • Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control Attacks attack class for patterns
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next Pirate x Pirate

The Pirate x Pirate hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial