Which versions of kmnb are malicious?

The following npm versions of kmnb are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate kmnb if I installed it?

Remove kmnb 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 kmnb — how do I know if it already compromised me?

If kmnb 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.

Is kmnb part of a known attack campaign?

Yes — kmnb is associated with the RLMA-2026-01394 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 kmnb across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kmnb (version 1.0.0).

Malicious package

kmnbnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

kmnb is a confirmed malicious npm package (MAL-2026-1767) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kmnb (npm)

MAL-2026-1767

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall kmnb

What this malware does

The package kmnb was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

287d509082247e576127664b9761a220311b0147f37a351695efb31292d7da91

403b1d663c5993d383034361edcd6d530aa6948d8cf17584e6d7a57917538a36

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for kmnb (version 1.0.0).
If you installed it — respond
Remove kmnb 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 kmnb 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. kmnb on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01394

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks kmnb-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

Explore

All malware advisories How O3 detects malware Vulnerability database