How much was lost in the NoOnes hack?

The NoOnes hack resulted in $7.9M in losses on January 01, 2025.

What attack technique was used in the NoOnes exploit?

The NoOnes exploit utilized Cross-Chain Message Spoofing. 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.

NoOnes Hack

TOTAL LOST $7.9M

Medium Jan 01, 2025 Cross-Chain Message Spoofing binance ethereum solana tron

Affected Chain binance 4 chains affected

Recovered - No recovery reported

All-Time Rank #399 By amount stolen

Year 2025 Incident year

Incident Report

Protocol / Project NoOnes

Date of Incident January 01, 2025

Affected Chain(s) binance ethereum solana tron

Attack Technique Cross-Chain Message Spoofing

Classification Bridge & Cross-Chain

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 cross-chain message spoofing and Rust/Anchor program internals and the Solana account model

Capital Required Seed capital to cover Solana network fees and initial position setup

On-Chain Access Ability to interact with binance, ethereum, solana, tron Solana programs and deploy a custom exploit program or signer account

Protocol Analysis Identification of the exploitable vulnerability in NoOnes's program logic - root cause: bridge & cross-chain

Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single Solana transaction (atomic across instructions)

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 Cross-Chain Message Spoofing audit checklist and test coverage

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

Verify all logic paths related to Cross-Chain Message Spoofing 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

Threat Assessment

Severity Level

MEDIUM

Attack Vector Cross-Chain Message Spoofing
Root Cause Bridge & Cross-Chain
Year 2025

Learn to Prevent the Next NoOnes

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