A Massive Crypto Heist: How a Simple Trick Led to a $282M Loss

A Shocking Heist

In a shocking turn of events, a crypto enthusiast recently lost a staggering $282 million in Bitcoin and Litecoin. This happened because of a clever trick known as social engineering.

The Incident

• Date: January 10, 2026, around 11:00 pm UTC
• Method: The victim was fooled into sharing their seed phrase, linked to a hardware wallet, giving the attacker full access to the funds.

The Attacker's Moves

The attacker wasted no time:

• Moved the stolen crypto across different networks to cover their tracks.
• Stole:
• 2.05 million Litecoin (LTC), worth $153 million
• 1,459 Bitcoin (BTC), worth around $139 million
• Converted stolen assets into Monero (XMR) using instant exchange services, causing its price to spike.
• Bridged large amounts of Bitcoin across Ethereum (ETH), Ripple (XRP), and Litecoin using THORChain, allowing them to shift value between blockchains without using centralized exchanges.

Security Firm's Response

Security firm ZeroShadow stepped in:

• Traced parts of the stolen funds in real time.
• Froze about $700,000 worth of funds before they could be fully swapped into privacy-focused assets.
• Identified the victim as someone tricked into sharing their seed phrase by an impersonator pretending to be Trezor “Value Wallet” support.

Expert Opinion

ZachXBT, a blockchain investigator, dismissed claims that the attack might be linked to a state-sponsored hacking group:

“It’s not North Korea.”

Previous Incidents

This isn't the first time such a heist has happened:

• Last year, an elderly US individual lost $330 million in Bitcoin in a similar social engineering scam.
• The victim had held more than 3,000 BTC since 2017 with little prior activity.
• The attacker laundered the Bitcoin using peel chains and multiple instant exchanges, ultimately swapping much of the stolen BTC into Monero to obscure its trail.

Important Lessons

These incidents highlight the importance of:

• Being cautious and verifying the authenticity of any support requests.
• Always double-checking before sharing sensitive information like seed phrases.