Updated 2026-11-15
Short answer: list the exact version of the package installed in each project with npm ls <package> --all or the lockfile, then check that name and version against the malware advisories in OSV and the GitHub Advisory Database, the same advisories npm audit returns. A clean result only means nobody has reported that version yet: for four malicious npm releases in 2026 the advisory appeared 50 minutes to 1 hour 44 minutes after the release, so for anything installed around an incident you also read what the package runs.
The version in package.json is a range. What counts is the version that was installed, including transitive dependencies you never added. StepSecurity found parent packages of @subql/common asking for ~5.8.2, a range that also accepts the malicious 5.8.3.
npm ls <package> --all npm explain <package> pnpm why <package> yarn why <package> grep -n -A3 '"node_modules/<package>"' package-lock.json git log -p --since=2026-11-01 -- package-lock.json
npm explain shows which dependency pulled a version in (Chainguard). The git log line shows when the lockfile changed, which tells you whether a bad version could have been installed during an incident. Projects you are not working on today count too:
find ~ \( -name package-lock.json -o -name pnpm-lock.yaml -o -name yarn.lock \) -not -path '*/node_modules/*' 2>/dev/null
GitHub publishes malware advisories automatically from the npm security team and the OpenSSF Malicious Packages repository. A malware advisory has no fixed version, because no version of a malicious package is safe (GitHub docs). npm audit sends your dependency list to the registry and reports known vulnerabilities; it needs a package-lock by default (npm docs). On 15 November 2026 the registry's bulk advisory endpoint, the one npm audit calls, returned a critical "Malware in keyv" advisory for keyv =6.0.0 and matching advisories for the other three versions in the table below. To ask OSV about one version without installing anything:
npm audit
npm audit --json
curl -s -X POST https://api.osv.dev/v1/query \
-d '{"package":{"name":"keyv","ecosystem":"npm"},"version":"6.0.0"}'For keyv 6.0.0 OSV answers with MAL-2026-11524, alias GHSA-3p9h-f68w-m6fx (checked 15 November 2026). On GitHub, search the Advisory Database for type:malware and the package name.
| Package | Bad version | On npm (UTC) | Advisory in OSV (UTC) | Gap | FixLane page |
|---|---|---|---|---|---|
| keyv | 6.0.0 | 4 Aug 2026, 09:35 | 11:19 | 1 h 44 min | incident 1758 |
| @subql/common | 5.8.3 | 5 Oct 2026, 11:56 | 12:46 | 50 min | incident 1767 |
| tensorlake | 0.5.144 | 8 Oct 2026, 01:12 | 02:54 | 1 h 42 min | in review |
| @ethersphere/bee-js | 13.3.0 | 9 Nov 2026, 00:09 | 01:25 | 1 h 16 min | incident 1907 |
Release times are from the npm registry's metadata, advisory times from the OSV API, both read on 15 November 2026. During each gap there was no advisory for npm audit to report. Dependabot has the same limit: GitHub says new malware may take time to appear in the Advisory Database and trigger alerts.
Research teams publish the bad versions and the files a payload leaves: Wiz for keyv, whose wave spread to more than 400 npm packages, and StepSecurity for @subql/common, tensorlake and @ethersphere/bee-js. The keyv guide and the Shai-Hulud guide list the files to search for. Other malicious npm packages FixLane has pages for: litecore-lib-ltc, the MemTensor memory plugin and indexed-btree.
Scripts that compare your lockfile with a bundled list only know the attacks from before their last release. scan-compromised 1.1.236, published 22 July 2026, ships a threats.json with 3,537 package names; on 15 November 2026 it had no entry for keyv, @subql/common, tensorlake or @ethersphere/bee-js. worm-sign 4.2.0, published 18 May 2026, covers the TanStack, Axios and Shai-Hulud 2.0 campaigns (its Socket page).
| Tool | What it checks | Fix guidance | What it needs | License |
|---|---|---|---|---|
| npm audit | The tree in your package-lock against registry advisories, malware included | npm audit fix installs versions without an advisory; malware advisories have no fixed version | Ships with npm | Part of the npm CLI |
| GitHub Advisory Database, Dependabot malware alerts | Your repository's default branch on GitHub | Alerts with suggested remediation steps | Alerts turned on for the repository | Database: CC-BY-4.0 |
| OSV-Scanner | Lockfiles, 19+ types, against OSV.dev | Experimental guided remediation (osv-scanner fix) | A downloaded binary, no key | Apache-2.0 |
| Socket CLI | Dependency scans through Socket's API, and npm or npx installs it wraps | socket fix for CVEs, security patches | An API token for scans | MIT |
| Snyk CLI | Project manifests with snyk test | Each vulnerability with its path and fix guidance | Install and authenticate with a Snyk account | Apache-2.0 |
| Aikido Safe Chain | Package downloads as they happen, through a local proxy, against Aikido Intel's malware feed; blocks packages newer than 48 hours | Blocks the download | An install script; free, no token | AGPL or commercial |
| FixLane | A package, program or CVE id against FixLane's verified incidents | A reviewed procedure per incident and OS through get_fix_prompt | Any MCP client or the Telegram bot, no account or key | Plugin: MIT |
Each row comes from the tool's own docs or repository, read on 15 November 2026.
npm view <package>@<version> scripts npm view <package> time --json npm approve-scripts --allow-scripts-pending npm audit signatures
scripts shows preinstall, install and postinstall. tensorlake 0.5.144 ran its payload from a preinstall hook (StepSecurity).time lists when each version was published, so you can compare your version with the date in an advisory.npm approve-scripts --allow-scripts-pending is read-only: it lists the packages whose install scripts are waiting for approval (npm docs).package.json and fires inside a prototype method when the app uses it (ReversingLabs).npm audit signatures verifies registry signatures and provenance attestations (npm docs). Provenance says where a package was built, not that it is safe: keyv 6.0.0 carried genuine SLSA provenance (Chainguard, citing Datadog Security Labs) and tensorlake 0.5.144 a valid npm provenance attestation (StepSecurity).npm pack <package>@<version>, extract it there and read it. Run nothing from it.Treat every machine and CI runner that installed the version as exposed: these payloads steal tokens and keys when they run (Wiz, StepSecurity). Do not start by revoking tokens. tensorlake installs a service that checks the stolen GitHub token every 60 seconds for up to 24 hours and runs rm -rf ~/ when GitHub rejects it (StepSecurity), and the keyv payload can arm the same kind of switch (Wiz). The safe order is in the Shai-Hulud guide. This page has no fix steps: FixLane serves the reviewed procedure for each incident, a read-only check first, through get_fix_prompt and the Telegram bot.
An AI agent connected to the free FixLane MCP server can run the read-only checks above and ask FixLane about each package. check_software for keyv returned this on 15 November 2026 at 17:50 UTC:
keyv - 1 known issue since 2026-08-01 · 1 exploited - keyv: Hijacked keyv and cacheable npm packages in a supply chain attack (incident 1758, unknown, exploited in the wild, published 2026-08-04, fix prompt available)
For packages, use check_software and compare your version with the one the incident names. check_inventory compares versions with verified fixed versions, and a malicious release has none, so the same day it answered keyv 6.0.0 with "unknown" and the related incident 1758 rather than "affected".
Yes, once an advisory exists. On 15 November 2026 npm's advisory endpoint returned a critical "Malware in keyv" advisory for keyv 6.0.0. Before the advisory is published it reports nothing: for four malicious npm releases in 2026 that gap was 50 minutes to 1 hour 44 minutes.
Run npm view <package>@<version> scripts to see its install scripts, and ask OSV: a POST to https://api.osv.dev/v1/query with the package name, npm and the version. A malicious version comes back with a MAL- id, for example MAL-2026-11524 for keyv 6.0.0.
No. Provenance shows where a package was built. keyv 6.0.0 and tensorlake 0.5.144 were both built from their real repositories and carried valid provenance.
Only for attacks from before the list was last updated. scan-compromised 1.1.236, published 22 July 2026, has no entry for keyv, @subql/common, tensorlake or @ethersphere/bee-js.
Do not revoke tokens first: some payloads delete your home directory when their stolen token is revoked. Treat the machine as exposed and follow the reviewed procedure for that incident, which FixLane serves through get_fix_prompt and its Telegram bot.
Connect an AI agent to the free, read-only FixLane MCP server or ask the Telegram bot: it checks what you have installed against verified fixed versions and serves a reviewed fix procedure. All guides.