Which versions of hyper-kube-config are malicious?

The following npm versions of hyper-kube-config are flagged malicious: 1.1.1. Treat any of these as compromised.

How do I remediate hyper-kube-config if I installed it?

hyper-kube-config is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed hyper-kube-config — how do I know if it already compromised me?

If hyper-kube-config 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 hyper-kube-config part of a known attack campaign?

Yes — hyper-kube-config is associated with the IN-MAL-2026-014849 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 hyper-kube-config 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 hyper-kube-config (version 1.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hyper-kube-config across your stack and pipelines.

Malicious package

hyper-kube-confignpm

hyper-kube-config is a confirmed malicious npm package (MAL-2026-12392) that steals credentials and exfiltrates sensitive data (malicious version 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hyper-kube-config (npm)

MAL-2026-12392

Immediate action

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

npm uninstall hyper-kube-config

What this malware does

package.json declares a preinstall hook that runs index.js on npm install. index.js collects the installer's hostname, username, home directory, DNS server configuration, current working directory, and the contents of /etc/passwd and /etc/hosts, then POSTs this payload over HTTPS to the hardcoded subdomain x75h3spwmlqq7bzriw6gm6w8azgq4hs6.oastify.com (a Burp Collaborator out-of-band interaction host). Execution is automatic at install time with no consent prompt and no documented purpose. The behavior matches a dependency-confusion reconnaissance beacon that exfiltrates installer host identity and local system files to an attacker-controlled endpoint.

Malicious versions

1 flagged

1.1.1

Indicators of compromise (SHA-256)

4e6e8d8500ee41d92250882b57d98d805b381d2d08eeeac7bae55c3f5e417dff

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hyper-kube-config (version 1.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hyper-kube-config across your stack and pipelines.
If you installed it — respond
hyper-kube-config is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If hyper-kube-config 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 hyper-kube-config 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. hyper-kube-config on npm has been identified as a malicious package (version 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014849

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hyper-kube-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database