Keystone's WhatsApp Warning: Separate Chat From Crypto
A trader says an attacker took control of his PC through WhatsApp Desktop, waited days, then closed his Hyperliquid positions and withdrew his funds. Keeping chat apps, passwords and crypto signing on one computer gave the reported compromise plenty to reach.
Keystone’s warning uses the incident to recommend a dedicated crypto device, stricter WhatsApp settings and an air-gapped hardware wallet. There’s useful advice there, but the claim that an automatic download caused a no-click takeover needs more evidence.
What the trader reported
In his original account, Harley Lewis Foote says the attacker accessed his MetaMask, email and passwords, closed his short positions, and moved funds through MetaMask to Tornado Cash. He says he was left with about $800. He doesn’t give a total loss figure.
In a follow-up, he says the payload came from an unknown WhatsApp number, auto-download had been enabled after an update, and he never clicked the file. He also reports a $10 test withdrawal before the larger theft.
These are the victim’s statements. The posts don’t establish the operating system, affected WhatsApp version or the mechanism that turned a downloaded file into control of the computer. In a further reply, Foote says a possible zero-click vulnerability was still being checked.
Downloading a file and executing malicious code are different steps. A flaw in automatic media processing can bridge that gap, but this account doesn’t identify one. It shouldn’t be presented as a confirmed new WhatsApp exploit, or as evidence that Hyperliquid’s protocol was hacked.
Change the WhatsApp settings, then separate the devices
WhatsApp’s Strict Account Settings is a documented feature. Meta says it blocks attachments and media from unknown senders and silences unknown callers, while restricting some app functionality.
On your primary phone, look under Settings > Privacy > Advanced > Strict account settings. Check the media auto-download controls in WhatsApp Desktop separately, and keep both the app and operating system updated. These precautions reduce exposure; they don’t establish how this theft happened or clean a computer that’s already compromised.
For a machine used to manage meaningful crypto holdings, keeping messaging apps and unsolicited downloads off it gives an attacker fewer routes in. A separate browser profile still shares the same operating system (easy to forget when the windows look separate).
If another computer isn’t practical, keep long-term holdings in a separate hardware-backed wallet and limit what the everyday trading wallet can access. Moving a browser wallet’s existing seed onto hardware won’t undo any earlier exposure of that seed.
A hardware wallet doesn’t protect every trading permission
Keeping the signing key inside a hardware wallet makes it harder for PC malware to steal that key. You still need to check what you’re signing on the device. Our crypto scam guide covers why a hardware wallet can’t rescue you from a harmful approval you’ve authorized.
Hyperliquid adds another distinction. Its API wallets, also called agent wallets, can act for an account without withdrawal permission. The official SDK example demonstrates an agent placing trades while lacking permission to transfer or withdraw funds.
That means protecting the main key can help protect withdrawals while an exposed trading key can still place losing trades or close positions. Collateral already on a trading platform remains exposed to the permissions you’ve granted. The public posts don’t establish which keys or permissions the attacker used here.
Keep savings separate from trading collateral, review authorized agents, and remove permissions you no longer need. An offline main key doesn’t make an online trading key harmless.