Melody Hack

TOTAL LOST $644K
Low Access Control

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #921 By amount stolen
Protocol Type Lending Target category

Incident Overview

Melody project was exploited for 2225 $BNB. The hacker was able to withdraw $SNS tokens using an off-chain vulnerability.

Melody is a GameFi and SocialFi project providing passive income opportunities to creative people. The project's signature check function was exploited by the attacker, which gained $SNS tokens and swapped them for 2225 $BNB. All the stolen amount was sent to another EOA address.

Attacker addresses:

https://bscscan.com/address/0xa3793ccb…7e43a0

https://bscscan.com/address/0x7ce402b6…25408a

https://bscscan.com/address/0x1e091ae0…cebdb7

Malicious transactions:

https://bscscan.com/tx/0x7fd61155…9dea8f

https://bscscan.com/tx/0xe10c76cb…b59e83

Incident Report

Protocol / Project Melody
Date of Incident
Attack Technique Access Control
Classification Gaming / Metaverse / Gaming / Metaverse / Gaming / Metaverse / Gaming / Metaverse / Gaming / Metaverse / Gaming / Metaverse / Gaming / Metaverse / Gaming / Metaverse / Gaming / Metaverse / Gaming / Metaverse / Gaming / Metaverse / Gaming / Metaverse / Gam

Protocol Information

Protocol Type Lending
Affected Token SGS
Official Website www.ammelody.com/
Protocol Twitter/X @Melody_SGS
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
Music 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 Melody'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 Melody, these are the critical security checks that could have prevented this incident (October 2022).

  • 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 Melody

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