GitHub flags version 0.5.1 of the npm package @lumen-labs-dev/whisper-node as malware, and npm no longer serves its code.
The package gives Node.js programs local speech-to-text with Whisper. The registry lists 17 earlier releases from September 2025.
What happened
npm published version 0.5.1 at 12:16 UTC on 21 October 2026.
- GitHub published malware advisory GHSA-8mqm-233x-2g2j for 0.5.1 on 22 October 2026, under CWE-506.
- OpenSSF copied it the same day as MAL-2026-18194.
- Amazon Inspector added a scan to that record on 29 October 2026. It reports that no static rule matched and that it saw no supply-chain behaviour.
- The registry also lists a version 1.0.0, published 16 minutes after 0.5.1. No advisory names it.
- The registry now serves only 0.4.0 and 0.4.1. The latest tag points to 0.4.1.
The code of 0.5.1 was unavailable for inspection because npm no longer serves it. No source describes a payload, domain or IP address.
Affected versions
0.5.1: malicious, says GHSA-8mqm-233x-2g2j.1.0.0: no advisory names it. npm no longer serves it.0.4.0and0.4.1: the advisory does not list them.
Indicators of compromise
- SHA-1 of
whisper-node-0.5.1.tgz, from MAL-2026-18194:f17035e2a1906469e308975a300988106f551b6c.
How to check
In a project folder, list every copy of the package.
npm ls @lumen-labs-dev/whisper-node --all
To search many projects at once, search the lockfiles.
grep -rn "@lumen-labs-dev/whisper-node" --include=package-lock.json --include=yarn.lock --include=pnpm-lock.yaml .
What to do now
- If you find 0.5.1, treat that computer as fully compromised. GitHub gives this advice.
- From a different computer, rotate every secret and key that the exposed computer stored.
- Remove the package. GitHub warns that removal does not guarantee that all malicious software is gone.
- Pin the dependency to a version the advisory does not list, such as 0.4.1, or remove the dependency.
What Vigilance would show
Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.
On the computer, at install
Vigilance blocked `@lumen-labs-dev/whisper-node` 0.5.1. This version is too new or changed in a way Vigilance must check first. The last safe version is 0.4.1. Install that version.
In the owner report
Bad update
@lumen-labs-dev/whisper-node 0.5.1
This update now downloads from the internet and runs other programs. The version before it did not.
- Ask the AI tool to swap @lumen-labs-dev/whisper-node to 0.4.1. That is the last safe version.
Frequently asked questions
Is @lumen-labs-dev/whisper-node safe to use?
GitHub flags 0.5.1 as malware. The advisory does not list 0.4.0 or 0.4.1, and the latest tag points to 0.4.1.
What does the malicious code in whisper-node 0.5.1 do?
No public source describes it. npm no longer serves the code of 0.5.1.