Which versions of kmf-bootstrap are malicious?

The following npm versions of kmf-bootstrap are flagged malicious: 100.100.100, 100.100.101, 100.100.102, 100.100.103, 100.100.106. Treat any of these as compromised.

How do I remediate kmf-bootstrap if I installed it?

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

If kmf-bootstrap 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 kmf-bootstrap part of a known attack campaign?

Yes — kmf-bootstrap is associated with the IN-MAL-2026-021398, IN-MAL-2026-021385, IN-MAL-2026-021388, IN-MAL-2026-021413, IN-MAL-2026-021426 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 kmf-bootstrap across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kmf-bootstrap (5 malicious versions).

Malicious package

kmf-bootstrapnpm

Advisory published Oct 9, 2026Updated Oct 11, 2026

kmf-bootstrap is a confirmed malicious npm package (MAL-2026-17746) that steals credentials and exfiltrates sensitive data (malicious versions 100.100.100, 100.100.101, 100.100.102…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kmf-bootstrap (npm)

MAL-2026-17746

Immediate action

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

npm uninstall kmf-bootstrap

What this malware does

On npm install, the package's postinstall script performs two exfiltration actions. First, it reads the installer's hostname and npm_package_name and issues DNS resolutions for a label of the form <host>.<pkg>.db4jlbku53082dmp0d7g3mffj7s7aordk.oast.me, leaking those identifiers to an Interactsh (oast.me) collaborator over DNS. Second, postinstall.js require()s a shipped Linux x64 native addon at prebuilds/linux-x64/addon.node that calls gethostname() and getpwuid()->pw_name and reads the npm_package_name and npm_config_registry environment variables, then opens a raw socket and sends an HTTP POST with body h=<host>&u=<user>&p=<pkg>&r=<registry> to the bare IP 64.181.165.115 (Host header 64.181.165.115, path /dc, HTTP/1.0, no TLS). The destination is a bare IP with no relation to the package publisher and the npm_config_registry value can disclose a private/internal registry URL from the installer's.npmrc. The native component is opaque code auto-executed during install with host-level network egress. The package name resembles the common 'bootstrap' naming convention, consistent with a dependency-confusion / typosquat lure whose purpose is to beacon successful installs and private registry metadata.

The OpenSSF Package Analysis project identified 'kmf-bootstrap' @ 100.100.102 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

5 flagged

100.100.100100.100.101100.100.102100.100.103100.100.106

Indicators of compromise (SHA-256)

4a4e085f9bdddf6800e613b7cdfeb6b2481b2fe9bf0ccb2a5b1bffad9538194b

cc9f15e56fb0bf13a7c0bb8ebfa0eeeaa376629272d6fed9073b9c338e1c6862

2405275a8f22c4e8d737c5bb93149a073ddecb6a6daf67715cb4bc2218f76161

746ee8923cc246b2816dd79a756552ce7975ae9305f195b502f9225a348e00ec

956976b01563579f32919e883c10229d2cf459fa2253ca34bd164fe83016a567

b95cb55a24f11248b1635861f0a10a3cb41bc4ee6ac7e2100439ca7c947bba74

dbbe7e819b6a360576d8c7ea55ef5da42e2bbb24596548235569fa9f8df6d646

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for kmf-bootstrap (5 malicious versions).
If you installed it — respond
kmf-bootstrap 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 kmf-bootstrap 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. kmf-bootstrap on npm has been identified as a malicious package (versions 100.100.100, 100.100.101, 100.100.102, 100.100.103, 100.100.106 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021398IN-MAL-2026-021385IN-MAL-2026-021388IN-MAL-2026-021413IN-MAL-2026-021426

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks kmf-bootstrap-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