Incident Overview
The project was holding a presale event using a separate smart contract:
https://www.bscscan.com/address/0xe9e3864f…7ab7f6#code
The final recipient was the token contract deployer, he received funds at:
https://www.bscscan.com/address/0x75b84a45…8fe5f7#internaltx
3,064 BNB, gathered from the presale, were transferred to the external wallet at:
https://www.bscscan.com/tx/0xc5899580…55f99d
The BNB recipient deposited funds into the Binance exchange:
https://www.bscscan.com/tx/0x229c02f4…250e67
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 Tin Finance, these are the critical security checks that could have prevented this incident (January 2021).
- 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 Tin Finance
The Tin Finance 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.