Crypto wallet drained: how it happens on a developer's Mac and what to do first
If you find a crypto wallet drained and its keys lived on a developer's Mac, look first for something that ran on that Mac and read the keys: a stealer, a fake extension or a malicious package. This page cannot advise on getting stolen funds back or moving what is left; for that, contact your wallet provider's or exchange's support. It covers stopping further loss: clean the Mac, change passwords and turn on MFA from another device you trust, and assume anything stored on the Mac, including a seed phrase, was read.
A seed phrase is the list of words that restores a wallet; a private key is the secret that signs transactions. Whoever has either one controls the money. Developers keep both next to code, tokens, extensions and packages, and each of those is a way in.
01What to do first after a crypto wallet drained
Do these in order.
- Stop using the Mac for anything sensitive. Stolen credentials and sessions let attackers keep acting without needing the original machine, so the loss can continue while the Mac looks normal.
- Clean the Mac. Remove login items, LaunchAgents and LaunchDaemons you do not recognize. LaunchAgents are small files that start programs in the background; they sit in ~/Library/LaunchAgents and /Library/LaunchAgents, and the system-wide ones in /Library/LaunchDaemons. Look for files you did not create. Consider a full clean reinstall of macOS. Do not restore from a backup or Time Machine image that may carry the stealer. How to check for an infostealer has the details.
- Change what was stored on the Mac, from another device. Change all passwords that were stored on it and enable MFA for important accounts. Do it from a second phone or laptop you trust, not from the infected Mac.
- Treat a seed phrase that was on the Mac as read. Never share a seed phrase with anyone, any code, or any bot.
- Revoke developer tokens. The malware used in fake job tests takes API tokens, cloud credentials and signing keys along with wallets. On GitHub, check the first step on GitHub account hacked before revoking anything. Other keys are on leaked API keys.
Browser sessions are part of the same loss; see cookie hijacking.
02Typical routes on a developer's Mac
These are the five routes behind a crypto wallet drained on a Mac like yours. The cases below the table show each one.
| Route | What happens | Example |
|---|---|---|
| Stealer started by the user | A fake installer, DMG or pasted Terminal command runs a stealer | AMOS, Banshee, Cthulhu |
| Fake editor extension | An extension from a public registry downloads and runs malicious code | Fake Solidity extension in Cursor |
| Malicious package | A package posing as a developer tool sends keys out | npm and PyPI packages, nodejs-smtp |
| Clipboard or address swap | Copied or destination wallet addresses are replaced | XCSSET, the September 2025 npm packages |
| Fake job test | A candidate runs a repository that harvests keys | Contagious Interview |
03The fake extension in Cursor
A blockchain developer had about $500,000 in crypto stolen after installing a fake Solidity extension in Cursor. His computer ran Windows, but the way in was the extension store, not the operating system. Cursor is an AI code editor, and it installs extensions from the Open VSX registry, a public extension store. The fake extension had none of its claimed features and only downloaded and ran malicious code. In search results it ranked fourth, while the legitimate one ranked eighth, so a search rank is not proof of anything. More cases are on malicious VS Code extensions.
04Why the Mac stays a problem after the loss
The theft does not end when the money moves. In one AMOS campaign the malware went from the first user interaction to persistent command and control within minutes. It also harvested Keychains, browser credentials and sessions from Chrome, Edge, Safari and Firefox, Apple Notes and documents. So a drained wallet can be the first thing you notice, not the only thing taken, and that is why steps 2 to 5 above matter even if the wallet is already empty.
05Packages that steal keys
A supply-chain attack is an attack through code you install.
- npm and PyPI packages posing as developer tools stole seed phrases and private keys. One npm package sent the stolen keys to Google Analytics disguised as ordinary telemetry.
- The package nodejs-smtp impersonated nodemailer and rewrote the Windows Atomic Wallet app's app.asar file to swap recipient addresses. The mailer still sent email, so tests passed.
- In September 2025, phishing of an npm maintainer put crypto-stealing code into 18+ packages. In browser wallets the malware changed the destination address before signing while still showing the original one.
06Stealers and fake job tests
Several Mac stealers go after wallets directly. Banshee targets browser credentials and crypto wallet extensions. Cthulhu shows a fake update dialog for the system password, then asks for a MetaMask password. AMOS was advertised with MetaMask brute-forcing and a crypto checker. XCSSET steals digital wallet data. The families are covered on Atomic Stealer and XCSSET.
Developers also get approached directly: fake recruiters from crypto trading or AI firms tell victims to clone and run an npm package from GitHub, GitLab or Bitbucket. The malware harvests API tokens, cloud credentials, signing keys, crypto wallets and password manager artifacts. The full story is on fake job interview malware.
07How to lower the risk
- Keep seed phrases and private keys away from code.
- Do not run copy-pasted commands from random pages or forums.
- Avoid unsigned DMGs and unofficial "terminal fix" tools.
- Use short-lived credentials and vaults instead of long-lived tokens in environment files.
- Check an extension or package before you install it, because a search rank is not a signal.
A stealer reads Keychain, browser stores, SSH keys, cloud credentials and wallet data, so unusual access to those is the thing worth alerting on. More on the family is on infostealers.
08Crypto wallet drained: what to remember
If the keys lived on the Mac, look for something that ran on it. Clean it, change credentials from another device you trust, and assume anything stored on that Mac was read. A wallet stealer starts as a program on the Mac; Artificial Immunity's free, open-source core watches program starts and reports what it finds.
FAQ
What to do if your wallet gets drained?
Stop using the Mac and clean it first: remove login items, LaunchAgents and LaunchDaemons you do not recognize, and strongly consider a full clean reinstall of macOS. Then, from another device you trust, change the passwords that were stored on the Mac and enable MFA. Assume the attacker has read anything you kept on that Mac, including a seed phrase.
What happened to the man who lost his crypto wallet?
A blockchain developer had about $500,000 in crypto stolen after installing a fake Solidity extension in Cursor. The extension did none of what it promised and only downloaded and ran malicious code. The details are on the VS Code extensions page.
Is it possible to recover a crypto wallet?
This page cannot help you get stolen funds back. It covers the part you can still control: stopping further loss by cleaning the Mac and changing credentials.
How does a crypto wallet get drained on a Mac?
Usually through malware you started yourself. These campaigns rely on user interaction and aim at credentials, session material and infrastructure secrets, and several families target wallet extensions and wallet data.
Can a wallet be drained through a code package?
Yes. npm and PyPI packages posing as developer tools have stolen mnemonic seed phrases and private keys.
Should I share my seed phrase with a support person or a tool?
No. A seed phrase and private key are the keys to your crypto assets, and they must never be shared with anyone, any code, or any bot.
Related guides
Sources
- Kaspersky Securelist, fake Solidity extension for Cursor
- Socket, npm and PyPI packages stealing wallet credentials
- Socket, nodejs-smtp impersonating nodemailer
- Check Point, the npm heist of September 2025
- Check Point, Banshee stealer
- Microsoft, XCSSET
- Microsoft, Contagious Interview
- Microsoft Defender Experts, hunting infostealers on macOS
- Unit 42, macOS stealers
- Cyble via SecurityAffairs, Atomic macOS Stealer
- Malwarebytes, AMOS cleanup guidance
- Artificial Immunity
- Cursor security notice, rotate from a trusted system