MonoSwap Hack

TOTAL LOST $1.3M
Medium Access Control

Summarize with AI

Affected Chain 2024 Incident surface
Recovered - No recovery reported
All-Time Rank #765 By amount stolen
Protocol Type Dexs Target category

Incident Overview

On July 24, 2024, MonoSwap suffered a hack after a developer was tricked into installing a phishing app while attempting to join a fake VC call. The phishing app infected the developer’s office PC with a botnet, which gave attackers access to MonoSwap’s wallets and smart contracts, allowing them to withdraw most of the staked liquidity.

The attack started when scammers impersonated venture capitalists (VCs) and invited a MonoSwap developer to a call. To join the fake call, the developer was instructed to download a malicious application from a phishing link (kakaocall.kr). Once installed, the app deployed a botnet onto the developer’s office PC, granting the attackers remote access to all MonoSwap-related wallets and contracts stored on the machine.

With this access, the hackers drained the majority of the liquidity staked in MonoSwap’s pools, directly impacting both the protocol and its users. MonoSwap is actively investigating the incident and urged all users to withdraw their positions immediately while also deleting an earlier post that accidentally contained the phishing link.

Incident Report

Protocol / Project MonoSwap
Date of Incident
Attack Technique Access Control
Classification Exchange (DEX)
Primary Source View Post-Mortem

Protocol Information

Protocol Type Dexs
Official Website www.moneyswap.io/
Protocol Twitter/X @MoonSwapDEX
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
BNB Chain Ecosystem

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 Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of MonoSwap's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
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? Likely — with a thorough Access Control audit checklist and test coverage

If you're auditing a protocol with similar architecture to MonoSwap, these are the critical security checks that could have prevented this incident (July 2024).

  • Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control 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 Trial

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next MonoSwap

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