NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

kdb1-demo-v2npm

Advisory published Updated

kdb1-demo-v2 is a confirmed malicious npm package (MAL-2026-117) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kdb1-demo-v2 (npm)

MAL-2026-117
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall kdb1-demo-v2

What this malware does

The package kdb1-demo-v2 was found to contain malicious 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

c1a20b2217012bae0720ec06b437e454ea9f37100cf6bbec5477a5460ff53424
2a67f080ec14c4f32313e33736b6b67e59accae55e5e2c388613df54d5b5c85d

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for kdb1-demo-v2 (all published versions).

  2. If you installed it — respond

    Remove kdb1-demo-v2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If kdb1-demo-v2 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. kdb1-demo-v2 on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2c3x-8jx5-g4wg

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks kdb1-demo-v2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

kdb1-demo-v2 (npm) malicious package — MAL-2026-117 | O3 Security