Which versions of kdb1-demo-v2 are malicious?

Every published version of kdb1-demo-v2 on npm is considered malicious. Remove the package entirely.

How do I remediate kdb1-demo-v2 if I installed it?

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.

I already installed kdb1-demo-v2 — how do I know if it already compromised me?

If kdb1-demo-v2 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is kdb1-demo-v2 part of a known attack campaign?

Yes — kdb1-demo-v2 is associated with the GHSA-2c3x-8jx5-g4wg campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find kdb1-demo-v2 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kdb1-demo-v2 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kdb1-demo-v2 across your stack and pipelines.

Malicious package

kdb1-demo-v2npm

Malicious code in kdb1-demo-v2 (npm) Remove it immediately and rotate any exposed credentials.

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kdb1-demo-v2 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kdb1-demo-v2 across your stack and pipelines.
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.
Did it already run?
If kdb1-demo-v2 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks kdb1-demo-v2 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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

github.com

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.

Malware detection Runtime egress monitoring