$ALI, $PUSH Tokens Phishing Hack

TOTAL LOST $4.4M
Medium Phishing

Summarize with AI

Affected Chain 2024 Incident surface
Recovered - No recovery reported
All-Time Rank #464 By amount stolen
Protocol Type Exploit/Phishing Target category

Incident Overview

Massive Loss: $4.39M of $ALI and $PUSH Tokens Lost to Crypto Phishing

A staggering $4.39 million worth of $ALI and $PUSH tokens were recently lost to a crypto phishing scam. The victim, identified by the address 0x7653c936…6a744e, fell prey to the scam orchestrated by scammers with addresses 0x84672cc5…9e29cd and 0x2ee9a175…621edb. The victim inadvertently signed a malicious Uniswap Permit2's Permit Batch message, facilitating the unauthorized transfer of tokens.

Notably, the token spender involved is a Safe wallet address.

Victim's Address: 0x7653c936…6a744e

Scammer 1 Address: 0x84672cc5…9e29cd

Scammer 2 Address: 0x2ee9a175…621edb

Exploit tx:

https://etherscan.io/tx/0xc943ea89…9417cc

Incident Report

Protocol / Project $ALI, $PUSH Tokens Phishing
Date of Incident
Attack Technique Phishing
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Phishing
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 Deep understanding of phishing and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in $ALI, $PUSH Tokens Phishing's contract logic - root cause: token
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
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 Phishing audit checklist and test coverage

If you're auditing a protocol with similar architecture to $ALI, $PUSH Tokens Phishing, these are the critical security checks that could have prevented this incident (March 2024).

  • Verify all logic paths related to Phishing are guarded by proper access controls and input validation - see the Phishing 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 Phishing Attacks examples →

Sources & References

Learn to Prevent the Next $ALI, $PUSH Tokens Phishing

The $ALI, $PUSH Tokens Phishing 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