Patex Hack
Incident Overview
The PATEX token recently experienced a rug pull incident, leading to a significant loss of approximately $121,664.74 USD in 499 BNB (WBNB) tokens.
The project team behind the PATEX token executed a rug pull by performing liquidity removal from the Pancake V2 pool. As a result, they successfully withdrew and transferred a total of 499 BNB (WBNB), equivalent to $121,664.74 USD, distributing the ill-gotten funds across four different wallets.
This sudden liquidity removal and token transfer event caught the community off guard, causing substantial financial losses to investors and holders of PATEX token.
Contract Creator:
https://bscscan.com/address/0x2c6275ae…d5852f
Liquidity Removal tx:
https://bscscan.com/tx/0x42a22f6b…14bfb2
Incident Report
Protocol Information
Market Context at Time of Hack
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to Patex, these are the critical security checks that could have prevented this incident (July 2023).
- Verify all logic paths related to Rugpull are guarded by proper access controls and input validation
- 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 TrialSecurity Audit History
- Audit Report 1 Report
Sources & References
Learn to Prevent the Next Patex
The Patex 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.