What does the kmz1 malware do?

The package kmz1 was found to contain malicious code. The OpenSSF Package Analysis project identified 'kmz1' @ 1.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of kmz1 are malicious?

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

How do I remediate kmz1 if I installed it?

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

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

How do I find kmz1 across my projects, lockfiles, and CI pipelines?

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

Malicious package

kmz1npm

Advisory published Dec 3, 2025Updated Dec 3, 2025

kmz1 is a confirmed malicious npm package (MAL-2025-191949) 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 kmz1 (npm)

MAL-2025-191949

Immediate action

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

npm uninstall kmz1

What this malware does

The package kmz1 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'kmz1' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2a6ae2284037ed233d5af5263950214a55a620b61dde2f0b12669eced34b1957

764e3cb5b5016e17afcd37b7b263ec2575af32008338ff14e72dd73b1d82bfa1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for kmz1 (version 1.0.0).
If you installed it — respond
Remove kmz1 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 kmz1 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. kmz1 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.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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