How much was lost in the MoveCash hack?

The MoveCash hack resulted in $133K in losses on May 30, 2023.

What attack technique was used in the MoveCash exploit?

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

MoveCash Hack

TOTAL LOST $133K

Low May 30, 2023 Rugpull

Affected Chain 2023 Incident surface

Recovered - No recovery reported

All-Time Rank #1428 By amount stolen

Protocol Type Exit Scam/Rugpull Target category

Incident Overview

Quick Summary

MoveCash token was rugpulled by the token deployer, which removed liquidity worth 133,215 $USD

Details of the Exploit

MoveCash is a BEP20 token trading on PancakeSwap. The token deployer removed all the liquidity from the pool, receiving 427 $BNB. Worth mentioning that initial liquidity was also added by the same deployer's address, which added 784 $BNB along with $MCA tokens.

All the stolen funds currently remain at the scammer's address.

Block Data Reference

Scammer address:

https://bscscan.com/address/0x31195051…96f9e6

Liquidity removal transaction:

https://bscscan.com/tx/0x26400c01…85aaec

Incident Report

Protocol / Project MoveCash

Date of Incident May 30, 2023

Attack Technique Rugpull

Classification Token

Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull

Affected Token MCA

Official Website www.mbl.cash/

Team Anonymous

Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories

Mineable

Protocol Links

GitHub

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 MoveCash'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 MoveCash, these are the critical security checks that could have prevented this incident (May 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/DeDotFiSecurity/status/1663540031150260226?s=20

Threat Assessment

Severity Level

LOW

Attack Vector Rugpull
Root Cause Token
Year 2023

Learn to Prevent the Next MoveCash

The MoveCash 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