Incident Overview
SCT project was rugpulled by its deployer, who sold the significant token supply resulting in a 90% dump of token price. The funds lost in this incident are 286,123 $USD.
SCT is a BEP20 token trading on PancakeSwap. The project experienced an exit scam as its deployer acquired some tokens from the sale but ended up selling all of them. The market sale resulted in a significant dump with over 90% decrease in token price and a loss of approximately 286,123 $USD.
Investigation revealed that the attacker moved funds along with those received from Gnosis Safe contract to drain liquidity pool through two transactions.
Deployer Address:
https://bscscan.com/address/0xbc4bbd9e…1233a9
Funds Holder Address:
https://bscscan.com/address/0xB8e11361…Ce1546
Draining Transactions:
https://bscscan.com/tx/0x619d34f4…30a407
https://bscscan.com/tx/0x8ea073c6…552494
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 SCT Token, these are the critical security checks that could have prevented this incident (June 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 SCT Token
The SCT Token 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.