Incident Overview
Flash loan exploit on TGBS contract resulted in a loss of approximately $151k.
The exploit targeted the TGBS contract (bsc 0xedecfA18…f950F4) through a flash loan scheme. The attacker took 1,229 BNB flashloan and executed multiple transactions, transferring a small amount of TGBS tokens to themselves. This action triggered a burning mechanism within the LP, resulting in the loss of approximately $151k.
After that funds were transferred through Tornado cash.
Exploiter:
https://bscscan.com/address/0xFF1db040…8f01E1
Attack TX:
https://bscscan.com/tx/0xa0408770…d4f2a4
Example of the Tornado deposit:
https://bscscan.com/tx/0xc979d047…a33852
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 TGBS, these are the critical security checks that could have prevented this incident (March 2024).
- Verify all logic paths related to Flash Loan Attack are guarded by proper access controls and input validation - see the Flash Loans 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 TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
Learn to Prevent the Next TGBS
The TGBS 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.