
Quick answer: on 12 November 2026 the US Department of Justice announced the seizure of cloud infrastructure used in a North Korean scheme the FBI calls FaceStealer. The attackers invite you to a video meeting from a hijacked account of someone you know, show a pre-recorded video of people you trust, then claim your audio is broken and hand you a "fix" that installs malware. The DOJ says it has led to the theft of more than $400 million in cryptocurrency in 18 months, and that open-source maintainers are now targets too. The defense is mostly habits: never run a "fix" during a call, check the meeting link, confirm odd requests on a second channel, and keep publishing rights off the machine you take calls on.
This article walks through the scheme step by step, using only what the DOJ and the Romanian outlet Libertatea published, then gives a checklist you can adopt this week. It does not claim that any specific person or project is affected.
What was announced
The DOJ press release is dated Thursday, 12 November 2026 and is titled "Justice Department Announces Actions to Disrupt North Korea's Massive Theft of Cryptocurrency" (justice.gov). The numbers it gives for FaceStealer:
| Item | What the DOJ says |
|---|---|
| Stolen through FaceStealer | More than $400 million in cryptocurrency, in the last 18 months |
| Evidence seized | Over 900 webcam videos of FaceStealer victims, under a federal warrant |
| Infrastructure | Cloud-based infrastructure used in the scheme was disrupted (Central District of California) |
| Separate action | More than $1.2 billion in cryptocurrency recently stolen from Binance was seized and restrained |
| Groups named | Sapphire Sleet, UNC1069, Dangerous Password, CryptoCore, APT38, BlueNoroff, Stardust Chollima |
Libertatea reported the story on 13 November 2026 (article, in Romanian). It describes more than 900 victims, more than $400 million stolen, fake meetings that imitate Zoom, Teams and Google Meet, and the fake audio fix. We cite the DOJ for the figures and use Libertatea for the platform detail and the Romanian-language coverage.
The part that matters for this audience: the DOJ says the hackers target people in cryptocurrency and web3, and have "increasingly targeted individuals involved in the development and maintenance of open-source software", trying to reach their devices and the software repository accounts they control. The DOJ describes this as targeting that "appears calculated to enable software supply-chain attacks." An FBI Los Angeles official is quoted saying the scheme can deceive "even the most experienced technical and security conscious computer user."
How the scheme works, step by step
This is the sequence as the DOJ describes it, with what each step is designed to exploit.
| Step | What happens | What it exploits |
|---|---|---|
| 1. The invitation | You receive a video meeting invite from an account the hackers took over from an earlier victim, so the sender is someone you know. | Trust in a familiar name |
| 2. The meeting | When you join, your webcam is recorded. The attackers play a pre-recorded video of a previous victim, or victims, you know, so trusted contacts seem to be present. Deepfake videos of well-known people in crypto and web3 are also used. | Trust in faces and voices |
| 3. The fake error | During the meeting a technical error is introduced, for example that you cannot be heard, with a link or prompt to fix it. | The habit of fixing audio quickly so a call can go on |
| 4. The "fix" | The fix installs malware on your computer. | Your own hands doing the install |
| 5. The wait | In several reported cases the theft of cryptocurrency and the hijacking of communication accounts happened months, or more than a year, after the first compromise. | Nobody connects a problem to a call from long ago |
| 6. The spread | The hackers access the new victim's contact lists, social media and messaging apps, then target the victim's personal and professional contacts. | Your contacts become the next invitations |
Step 2 matters most: your own webcam footage can become the "trusted contact" shown to the next person. And step 5 means a quiet week after the call proves nothing.
Why developers and maintainers are exposed
A maintainer's laptop usually holds more than personal files. It can hold a signed-in GitHub session, SSH keys, npm or PyPI publish tokens, cloud credentials and the keys to a CI pipeline. If an attacker controls that machine, they do not need to break into the repository. They can publish as you.
That is why the DOJ's wording about supply-chain attacks matters. A single compromised maintainer account can put a malicious release in front of everyone who installs the package. Small companies face the same risk through one laptop or one long-lived deploy key.
The DOJ does not publish a count of affected maintainers.
The checklist that stops it
None of these steps needs a new product. Each one breaks a link in the chain above.
Before the call
- Treat the invitation as unverified, even from a friend. The invite may come from a stolen account. If a contact you rarely hear from suddenly asks for a call, ask on a different channel, such as a phone number you already had or a different messaging app, whether they really sent it.
- Check the meeting link before you click. Zoom, Teams and Google Meet each use their own domains. Libertatea reports that the scheme uses clones of these platforms, so read the full domain, not the displayed text, and prefer opening the platform's own app and entering the meeting ID yourself.
During the call
- Never install, download, paste or run anything to fix a call. This is the single rule that defeats step 3 and step 4. If your audio fails, leave the call, restart your own app, switch to another device, or reschedule. A legitimate platform does not need you to run a command or a downloaded file in the middle of a meeting.
- Be wary of a call that feels off. The DOJ says pre-recorded video and deepfakes are used, so a person who does not react to what you say or cannot answer an unexpected question is a warning sign. End the call.
- Confirm unusual requests on a second channel. Any request to share a screen, install a tool, move funds, share a token or approve access gets a confirmation through a channel the attacker does not control.
On your machines and accounts
- Keep publishing rights off the machine you take calls on. Use a separate machine, user profile or container for releases to npm, PyPI and your package registries. The laptop where you accept video invitations should not hold the keys to publish.
- Use hardware security keys or strong two-factor authentication on GitHub, npm and PyPI. A key that must be physically touched is much harder to use from a stolen session than a code from an app. Check each platform's current options in its own settings.
- Use short-lived, narrowly scoped tokens. A publish token that expires and can only publish one package limits what a thief can do. Remove old tokens you no longer use.
- Update your operating system and browser from their own settings, never from a link sent in a chat.
If you already clicked
Because the DOJ describes theft months after the first compromise, assume a click may matter later. These are sensible general steps; the FBI said it published a report with best practices and steps for victims, which is the authoritative place to check (FBI report, linked from the DOJ release).
- Disconnect the machine from the network and stop using it for sensitive work.
- From a different, clean device, change passwords and revoke sessions and tokens for email, GitHub, npm, PyPI, cloud consoles and your password manager.
- Rotate keys that were on the machine: SSH keys, API keys, signing keys and deploy keys.
- Check recent releases and access logs for publishes or changes you did not make.
- Warn your contacts, because the scheme uses your contact lists to reach them.
- Reinstall the operating system rather than cleaning it, and restore only data you trust. If money or crypto is involved, report it to the relevant authorities.
How we work, in one honest line
Devaland works asynchronously and in writing, which removes the "quick call to fix your audio" lever this scheme depends on. Nothing we do requires you to join a live call or install something during one. If you want a second pair of eyes on how your own build, publishing and token setup holds up, see our AI development page, or our information security page for how we handle data.
Frequently Asked Questions
What is FaceStealer? It is the name the FBI uses for a North Korean social engineering scheme. Victims are invited to a video meeting from a hijacked account, shown recorded or deepfake video of people they trust, and then told to install a fix for a fake technical error that installs malware. The DOJ announced actions against it on 12 November 2026.
How much has FaceStealer stolen? The DOJ says the scheme resulted in the theft of more than $400 million worth of cryptocurrency in the last 18 months. The DOJ also reports a separate seizure of more than $1.2 billion in cryptocurrency stolen from Binance. These are the DOJ's figures, announced on 12 November 2026.
Are open-source maintainers targeted? Yes, according to the DOJ. It says the hackers have increasingly targeted people who develop and maintain open-source software, trying to reach their devices and the software repository accounts they control. The DOJ describes this as appearing calculated to enable software supply-chain attacks. It does not give a count of affected maintainers.
What is the safest rule to follow during a video call? Never install, download or run anything to fix a call. If audio or video fails, leave the call and restart your own app, switch devices or reschedule. This one rule breaks the step where the malware is installed, because the scheme depends on you running the "fix" yourself.
What should I do if I already installed the fix? Disconnect the machine, then from a clean device change passwords and revoke sessions and tokens for email, GitHub, npm, PyPI and cloud accounts. Rotate keys that were on the machine, check recent releases for changes you did not make, warn your contacts and reinstall the system. The FBI published a report with victim steps.
Sources: US Department of Justice press release, 12 November 2026; Libertatea, 13 November 2026. Figures are quoted as published on those dates.