Which versions of kubernetes-helm are malicious?

Every published version of kubernetes-helm on npm is considered malicious. Remove the package entirely.

How do I remediate kubernetes-helm if I installed it?

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

If kubernetes-helm 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 kubernetes-helm across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kubernetes-helm (all published versions).

Malicious package

kubernetes-helmnpm

Advisory published Dec 1, 2025Updated Dec 1, 2025

kubernetes-helm is a confirmed malicious npm package (MAL-2025-191514) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kubernetes-helm (npm)

MAL-2025-191514

Immediate action

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

npm uninstall kubernetes-helm

What this malware does

The package kubernetes-helm was found to contain malicious code.

Malicious versions

all versions

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

Indicators of compromise (SHA-256)

d507ab92764d5a31189e5fc42060eca5ba9b17fd8fc4d35de9ad266c1eb63144

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for kubernetes-helm (all published versions).
If you installed it — respond
Remove kubernetes-helm 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 kubernetes-helm 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. kubernetes-helm 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.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks kubernetes-helm-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