The Onigiri Neko Hack
Incident Overview
The ONIGI token recently experienced a rug pull incident, leading to a loss of approximately $10,000 USD in ONIGI tokens.
The project team behind the The Onigiri Neko token executed a rug pull by calling withdrawOnigiri(uint256 _amount) function. After this tokens were sent to another EOA 0xfDE9a and swapped to the WETH.
Contract Creator: 0xF0db9ab3…A42573
Example withdrawOnigiri tx:
https://etherscan.io/tx/0x818afd0e…58de0d
https://etherscan.io/tx/0x2f25072a…e633c4
Sell TX example:
https://etherscan.io/tx/0x5d64a650…980690
Incident Report
Protocol Information
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 The Onigiri Neko, 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 TrialSources & References
Learn to Prevent the Next The Onigiri Neko
The The Onigiri Neko 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.