npm package report

Is keyv safe?

Version 6.0.0 of keyv was compromised. Other versions are not flagged as malicious.

Do not install keyv 6.0.0

CRITICAL

Compromised releases. Added to CyberXYZ 2026-08-04, OSV malicious-package feed (Google / OpenSSF).

// what we observed

npm/keyv version 6.0.0 is a trojanized release published on 2026-08-04 during the compromise of the npm/GitHub maintainer account behind the keyv and cacheable package families (user "Jaredwray"). Attackers pushed the malicious payload to the source repository and cut releases through GitHub Actions, so the poisoned versions reached npm with a valid, signed provenance attestation (provenance attests build integrity, not source integrity). Delivery is through the npm install lifecycle: the trojanized package.json adds a preinstall hook ("preinstall": "node setup.mjs") that runs before any project code on a bare npm install, while the normal compiled output is left intact so the package still works after install. setup.mjs downloads a standalone Bun runtime and uses it to run a second stage (shipped as Math_Symbol.js, a heavily obfuscated ~728 KB Bun bundle, referenced at runtime as math_init.js). The stealer harvests credentials from cloud instance metadata (AWS IMDS at 169.254.169.254, ECS at 169.254.170.2, GCP, Azure), AWS/GCP/Azure keys, HashiCorp Vault tokens, Kubernetes service-account tokens, GitHub Actions OIDC and org/repo secrets, and npm tokens, with a TruffleHog-style regex sweep for further secrets and private keys. Using the stolen npm identity (including npm OIDC trusted publishing) it enumerates and republishes further packages the token can reach — which, for a maintainer controlling both keyv and cacheable, gave the worm a large blast radius. Stolen findings are exfiltrated to attacker-created GitHub repositories (descriptions reading "Shai-Hulud: Here We Go Again") and to destinations resolved over DNS, and autostart hooks are planted in the repository's .claude/ and .vscode/ configuration to run the loader when a developer or AI coding agent opens a clone. Treat any environment that installed this version (with install scripts enabled) as fully compromised and rotate every reachable credential. Part of the August 2026 npm worm that poisoned 400+ packages across many organizations. keyv@6.0.0 is a lookalike of the popular keyv key-value package but ships an attack chain absent from the real library. The package.json preinstall hook runs a heavily obfuscated setup.mjs whose strings (URLs, shell commands, platform tokens, payload filename) are all reconstructed at runtime via a rotated string-array plus RC4-style decoder. On install, setup.mjs reassembles a GitHub-releases URL for a platform-specific Bun runtime archive (bun-linux-, bun-darwin-, bun-windows-*), downloads it, extracts it via PowerShell Expand-Archive or unzip, chmod+x's the resulting binary, and then uses execFileSync to invoke the shipped Math_Symbol.js under that dropped Bun runtime. Math_Symbol.js is a ~727 KB Bun-compiled bundle (// @bun @bun-cjs prelude) with obfuscated identifiers and a large constant table; it is not referenced by dist/index.mjs and only ever runs under the alien Bun runtime dropped at install. The library's advertised key-value storage has no need for a second language runtime or a hidden compiled bundle. Installing this package causes attacker-controlled code to execute on the installer's machine automatically via the npm preinstall lifecycle, using an alien-runtime dispatch that evades scanners inspecting only Node-resolved code. Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Reported by Amazon Inspector and GitHub Advisory Database via OSV.

// versions and what to do
Malicious
6.0.0
Move to
6.1.0 newest 6.x release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install keyv@6.1.0

OSV recordreferencereferencereferencereferencereferenceadvisory

// reach

1 direct dependencies

none carry a known advisory

    15 packages depend on it

    an advisory here reaches each of them

    Create a free accountfor every dependency path, dependent and what to upgrade
    // ai model usage

    Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.



    Checked 2026-10-30 at 23:59 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.

    Think a verdict here is wrong? Tell us — we respond within 2 business days.