How much was lost in the Social Engineering Scam hack?

The Social Engineering Scam hack resulted in $282M in losses on January 10, 2026.

What attack technique was used in the Social Engineering Scam exploit?

The Social Engineering Scam exploit utilized Phishing. 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.

Social Engineering Scam Hack

TOTAL LOST $282M

Critical #38 All-Time Jan 10, 2026 Phishing

Affected Chain 2026 Incident surface

Recovered - No recovery reported

All-Time Rank #38 By amount stolen

Protocol Type Exploit/Phishing Target category

Incident Overview

Quick Summary

On January 10, 2026, a victim lost over $282 million worth of Bitcoin and Litecoin (1,459 BTC and 2.05M LTC) through a hardware wallet social engineering scam, with the attacker immediately bridging 928.7 BTC (~$71M) via THORChain to Ethereum (19,631.1 ETH), Ripple (3.15M XRP), and Litecoin (77.2K LTC), then laundering portions through Tornado Cash and multiple centralized exchanges.

Details of the Exploit

ZachXBT reported this massive theft occurring around 11 PM UTC on January 10, 2026, where social engineering tactics were used to compromise the victim's hardware wallet containing substantial Bitcoin and Litecoin holdings. The attacker immediately began converting the stolen assets through multiple channels to obscure the trail. A significant portion (928.7 BTC worth approximately $71M) was bridged through THORChain's cross-chain swap protocol, converting to 19,631.1 ETH on Ethereum, 3.15M XRP on Ripple, and 77.2K LTC.

The attacker also converted substantial amounts of the stolen LTC and BTC directly to Monero via multiple instant exchanges, causing the XMR price to sharply increase due to the volume. From the Ethereum-bridged funds, the attacker dispersed assets to various destinations including 1,468.66 ETH ($4.9M) laundered through Tornado Cash, 735 ETH ($2.4M) to WhiteBit, 100 ETH to ChangeNOW, 2,402 ETH ($8M) to KuCoin, and 143 ETH ($477K) to Huobi, employing a multi-layered laundering strategy combining privacy protocols, instant exchanges, and centralized platforms.

Block Data Reference

Theft Addresses:

bc1qluxw46r55wf3dnk9c652vrt4duadm3hpuktf86 (BTC)

bc1qpsmh26ja0fzzf286zulmt9eywujc2pggj40wzm (BTC)

ltc1qly43c2prj4c2e85dcspzpjd36jnapnenldnr70 (LTC)

This is classified as a Phishing Attacks . Compare similar hacks →

Incident Report

Protocol / Project Social Engineering Scam

Date of Incident January 10, 2026

Attack Technique Phishing

Classification Other

Primary Source View Post-Mortem #1 View Post-Mortem #2 View Post-Mortem #3

Protocol Information

Protocol Type Exploit/Phishing

Team Anonymous

Source Code Unverified

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 phishing 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 Social Engineering Scam's contract logic - root cause: other

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? Likely — with a thorough Phishing audit checklist and test coverage

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

Verify all logic paths related to Phishing are guarded by proper access controls and input validation - see the Phishing 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 Phishing Attacks examples →

Phishing Attacks

Sources & References

01
Source 1 https://x.com/PeckShieldAlert/status/2013171957135733060
02
Source 2 https://x.com/MetaEraHK/status/2013196925743612276
03
Source 3 https://t.me/investigations/302

Threat Assessment

Severity Level

CRITICAL

Attack Vector Phishing
Root Cause Other
Year 2026

Learn to Prevent the Next Social Engineering Scam

The Social Engineering Scam 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