link.png

ID:

pirate-x-pirate-44

Date:

Status:

Incident Count:

March 9, 2022

Verified

1

info.png
target.png
REKT

Contributor:

chain.png

zerofriction.io

KYC By:

KYC:

No

info.png

Audit By:

Audits:

None

Loss Amount:

85,528

info.png

Recovered:

-

Rewards:

Currency:

USD, BNB, PXP

info.png

Key Indicators

Platform:

Type:

Category:

Method:

Data Sources:

Binance Smart Chain

Chain Game

GameFi

Key Management

Extended Method:

Private key leak, hot wallet

info.png

Days in Operation:

194

(0.53 Years)

chain.png
chain.png
chain.png
chain.png
datasource.png

The staking contract of Pirate X @PXPNFTsGame has been attacked. BlockSec suspects it's due to the private key leakage (since the attacker leveraged a valid signed message to launch the attack). Specifically, the staking contract of Pirate X Pirate (0x6912B19401913F1bd5020b3f59EE986c5792DA54) was attacked by an attacker, resulting in the loss of the PXP token.

When user deposit their PXP token into this contract, their token will be transferred into an EOA account (0x3b74a9cb5f1399b4a5a02559e67da37d450067b7). The contract will call `Transferfrom` to transfer these funds back when user withdraw their tokens.

When users withdraw their funds, they will submit a signature signed by a singer controlled by the project. The attacker provided a valid sign of the external signer (0x7435e0e4c4d10988e8821dc4853d1db2eceb176d) and withdraw 9,681,000 PXP tokens.

The attacker dumped these tokens into the market, got a profit of about 212 BNB.

info.png

DISCLAIMER: While web3rekt has used the best efforts in aggregating and maintaining this database, this web site makes no representations or warranties with respect to the accuracy or completeness of its information and data herein, and specifically disclaim any implied warranties of merchantability or fitness for any particular purpose. 

Under no circumstances, shall web3rekt be liable for any loss of profit or funds, any regulatory or governmental penalties, any legal costs, or any other commercial and non-commercial damages, including but not limited to special, incidental, consequential, or other damages from any or all usage of the data and information derived from this database.