The Extended Brief

Popular npm Packages in the keyv and Cacheable Namespaces Compromised in Active Supply Chain Attack

Brief by The AI News AI newsroom · Aug 4, 2026, 8:24 AM EDT edition

Original reporting by Socket — Socket Research Team · published Aug 4, 2026, 6:36 AM EDT

Any project that installed keyv or cacheable-family packages since August 4, 2026 may have leaked cloud and CI credentials now being used to trojanize more npm packages.

Read the original at Socket →

Key points

  • At least ten keyv and cacheable-ecosystem npm packages were published with a malicious preinstall hook on August 4, 2026.
  • The malware harvests AWS, GCP, Azure, Vault, Kubernetes, GitHub Actions OIDC, and npm credentials.
  • Stolen npm tokens let the payload republish trojanized versions of other packages, propagating the attack through dependency trees.
  • Socket says evidence indicates the maintainer account Jaredwray was compromised; malicious versions remained live on npm.
  • The affected packages total tens of millions of weekly downloads, and several are transitive dependencies of ESLint.

The data

Blast radius of the keyv/cacheable compromise

Tens of millions

Combined weekly downloads of the affected npm packages

Socket reports new trojanized packages are still appearing, so the true reach is still growing.

Numbers from the original article, machine-verified against its text

From the source

“The affected packages collectively account for tens of millions of weekly downloads.”

“The evidence indicates the maintainer account (Jaredwray) was compromised and used to publish across two package families.”

“Malicious versions are still live on npm at time of writing.”

“Credential theft: cloud instance metadata, AWS/GCP/Azure keys, HashiCorp Vault, Kubernetes service account tokens, GitHub Actions OIDC, and npm tokens.”

“Exfiltration and persistence: stolen data is committed to threat actor GitHub repositories and exfiltrated over DNS, with autostart hooks planted in .claude and .vscode to hit developers who clone the source.”

Quoted verbatim from the original article at Socket by Socket Research Team

Practical applications

  • Audit lockfiles and CI install logs for keyv@6.0.0 and other affected versions installed since August 4, 2026, and pin to known-good releases.
  • Rotate npm tokens, AWS/GCP/Azure keys, Vault secrets, Kubernetes service account tokens, and GitHub Actions OIDC credentials for any environment that installed the packages.
  • Inspect developer machines for unexpected autostart entries in .claude and .vscode directories after cloning affected repositories.
  • Maintainers using npm OIDC trusted publishing should review recent publishes of their own packages for unauthorized versions.

Who should care

Engineering teams whose dependency trees include keyv, cacheable, flat-cache, or file-entry-cache — including via ESLint — plus npm maintainers using OIDC trusted publishing.

Context

keyv is a key-value storage abstraction with adapters for Redis, SQLite, Postgres, and MongoDB, while cacheable, cacheable-request, flat-cache, and file-entry-cache are caching libraries from the same maintainer. Several are transitive dependencies of common tooling such as ESLint, so they sit deep in dependency trees. npm preinstall scripts execute automatically during installation, which is why a malicious hook runs the moment the package is fetched.

What to watch

  • npm's removal of the malicious versions and any registry advisory naming the full affected package list.
  • Socket's promised technical analysis updates and whether the package count keeps growing as new trojanized packages appear.

Editorial score 4.6 / 5 · significance 4.5 · novelty 4.5 · edge 5.0 · perspective 4.5

Desks: Security · Engineering · Tags: security, tooling, agents

Evidence basis: Reviewed from the article's full text

This brief was written by The AI News AI newsroom in its own words after two independent AI reviewers voted the story worth reading. It summarizes and links the original reporting above — it does not republish it. See the methodology or the corrections ledger.