UFCT Hack

TOTAL LOST $1.3M
Medium Rugpull

Summarize with AI

Affected Chain 2021 Incident surface
Recovered - No recovery reported
All-Time Rank #769 By amount stolen
Protocol Type Exit Scam/Rugpull Target category

Incident Overview

The project was holding a fundraising event:

https://cointool.app/ido/exchange?id=236b257521232075502150272572237071232a2b2a26762321242322272522262222242652552b762b726f2625

Based on the on-chain data, the token contract deployer was a fund recipient from all presale contracts:

https://bscscan.com/address/0x1a242dfe…93095c#internaltx

Stolen funds were transferred on the external wallets at:

https://bscscan.com/tx/0x5d4bb28d…cc4f79

https://bscscan.com/tx/0xbc3022e5…b89fde

https://bscscan.com/tx/0x4334277e…96cdc6

https://bscscan.com/tx/0xd7d50526…acf5dd

https://bscscan.com/tx/0xafd02763…d73dec

https://bscscan.com/tx/0x0815483a…a32918

https://bscscan.com/tx/0xcd69e3fe…3b0148

https://bscscan.com/tx/0x91da9be6…804866

https://bscscan.com/tx/0xe7889a7b…783b7b

https://bscscan.com/tx/0x3dc3e0e4…342e41

https://bscscan.com/tx/0xde56b5ef…7f4321

https://bscscan.com/tx/0x7434916a…47b4e0

https://bscscan.com/tx/0x1c9e84c8…f140f1

https://bscscan.com/tx/0x27059dcb…0755c6

https://bscscan.com/tx/0xfd2ae9c2…69d4db

Incident Report

Protocol / Project UFCT
Date of Incident
Attack Technique Rugpull
Classification Token

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token UFCT
Official Website ufccryptogame.com/
Team Anonymous
Source Code Unverified

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.

Technical Knowledge Deep understanding of rugpull and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in UFCT's contract logic - root cause: token
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Hard to catch — private key / OpSec failures are outside smart contract audit scope

If you're auditing a protocol with similar architecture to UFCT, these are the critical security checks that could have prevented this incident (November 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 Trial

Sources & References

Learn to Prevent the Next UFCT

The UFCT 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.

Recreate exploit patterns safely Free Trial