How much was lost in the FCS hack?

The FCS hack resulted in $2.6M in losses on January 04, 2023.

What attack technique was used in the FCS exploit?

The FCS exploit utilized Rugpull. Understanding this attack vector is critical for smart contract auditors and developers building secure DeFi protocols.

How can developers prevent similar smart contract attacks?

Preventing smart contract hacks requires a combination of secure coding practices, thorough security audits, and understanding common attack vectors like reentrancy, oracle manipulation, and access control flaws. Smart Contract Hacking (SCH) provides hands-on training to help developers and auditors identify and prevent vulnerabilities before deployment.

FCS Hack

TOTAL LOST $2.6M

Medium Jan 04, 2023 Rugpull

Affected Chain 2023 Incident surface

Recovered - No recovery reported

All-Time Rank #589 By amount stolen

Protocol Type Exit Scam/Rugpull Target category

Incident Overview

Quick Summary

FCS Token was rugged by the protocol MasterChefs' owner. The scammer's profit is 2,588,000 $USD.

Details of the Exploit

The MasterChef contract contains a backdoor for withdrawing reward token FCS withdrawSushiReward(address recipient, uint256 amount). This function was executed by the contract owner on Jan-04-2023. Then FCS tokens were swapped to FUT tokens and then to USDT.

Currently, all USDT tokens sit in one of the scammers' addresses.

Block Data Reference

Rug TX:

https://bscscan.com/tx/0x9ffb8046…252c68

Owner address:

https://bscscan.com/address/0x1bb991b2…f46c21

USDT tokens were transferred to the address:

https://bscscan.com/address/0xbdb9509e…ce1bd6

Incident Report

Protocol / Project FCS

Date of Incident January 04, 2023

Attack Technique Rugpull

Classification Token

Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull

Affected Token FCS

Official Website www.fecessolana.com

Protocol Twitter/X @fecessolana

Team Anonymous

Source Code Unverified

Market Context at Time of Hack

Token Categories

Solana Ecosystem

Protocol Links

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 FCS'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 FCS, these are the critical security checks that could have prevented this incident (January 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 Trial

Sources & References

01
Source 1 https://twitter.com/PeckShieldAlert/status/1610598038388740098

Threat Assessment

Severity Level

MEDIUM

Attack Vector Rugpull
Root Cause Token
Year 2023

Learn to Prevent the Next FCS

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

Start Free Trial Browse Attack Library