@dinhhoangg1991

⚠️⚠️ WALLET HACKED FOR USING HOTEL WIFI!! @the_smart_ape recounts a story that sends chills down your spine – and many crypto enthusiasts will see themselves in it. He went on a 3-day vacation to a pretty fancy hotel with his family. He brought his laptop with the intention of "doing some work for fun." His wife advised against it, but like many crypto addicts, he still turned it on. He connected to the hotel's Wi-Fi. No password, just a captive portal. Everything seemed normal: browsing X, checking wallet balance, Discord, Telegram. No new wallets created, no strange links clicked, no frivolous dApps accessed. 📱 Then he received a phone call from a friend in crypto. They talked about the market, BTC, Phantom wallet, swap on Jupiter… And he had no idea that someone nearby was eavesdropping. This person realized he was using Phantom, holding assets, and became a target. The problem lay in public Wi-Fi. On the same network, devices "see" each other more than he realized. The attacker performed a man-in-the-middle attack – standing between him and the internet, silently injecting malware into the website he was visiting. 🧑‍💻 When he accessed Jupiter Exchange to swap, the interface appeared normal. But behind the scenes, the malware had interfered. Instead of a familiar swap command, the Phantom wallet displayed a different request: "Authorize," "Approve account," "Confirm session." There was no money. No immediate SOL transfer. Just a seemingly harmless technical request. Because he was swapping on Jupiter, he carelessly clicked approve. In reality, it wasn't a money transfer, but permission granting. He had given another address the right to act on his behalf. The attacker didn't do anything immediately. He waited a few days, after the victim left the hotel, before withdrawing his $SOL, transferring the tokens and NFTs to another wallet. 📌 Result: He lost about $5,000 from a secondary hot wallet. Not his main wallet, but still extremely frustrating. Ultimately, he admitted his mistake: > He shouldn't have used public Wi-Fi; he should have turned on a hotspot from his phone. > He shouldn't have talked about crypto in public. > And especially: he should have read any wallet signing requests extremely carefully, even on familiar apps. Because the request might have been intercepted midway and didn't actually come from where he thought. It's not a new story, but it's still very easy to fall victim to. And in most cases, just one moment of carelessness is enough.

0 reply

0 recast

0 reaction