Which versions of khanbmnxls are malicious?

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

How do I remediate khanbmnxls if I installed it?

khanbmnxls is a typosquat — you almost certainly intended a legitimately-named package. Remove khanbmnxls, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed khanbmnxls — how do I know if it already compromised me?

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

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

Malicious package

khanbmnxlsnpm

khanbmnxls is a confirmed malicious npm package (MAL-2026-13820) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in khanbmnxls (npm)

MAL-2026-13820

Immediate action

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

npm uninstall khanbmnxls

What this malware does

The package contains a single index.html that impersonates a Cloudflare Turnstile 'Just a moment...' challenge page. The inline JavaScript is heavily obfuscated (obfuscator.io-style _0xNNNN identifiers and a shuffled string array) and assembles a redirect URL beginning with https://kh from decoded string fragments, wired to a fake data-sitekey and an onTurnstileComplete callback. The package declares no npm lifecycle scripts (no preinstall/install/postinstall/prepare), no JavaScript main, and no bin entry, so npm install and require() of this package do not execute the HTML or its embedded script. The harm surface is limited to a browser that renders the file directly; developers installing the package from npm are not attacked at install or import time. The artifact is a phishing/redirect lure hosted on the npm registry rather than a functional Node package.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

30db27aba41dd5dea17f1a3454277a9482c18d34fd9cd5d2ac8af1d8ea8f4eb0

2170fddb23040b2e55eeeb17188244072efdef033879036b45865f5b84ef7346

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for khanbmnxls (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging khanbmnxls across your stack and pipelines.
If you installed it — respond
khanbmnxls is a typosquat — you almost certainly intended a legitimately-named package. Remove khanbmnxls, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If khanbmnxls 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 khanbmnxls 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. khanbmnxls 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

GHSA-f4qx-qcrw-f6f5IN-MAL-2026-017485

References

Credits

Amazon Inspector · finder

Detect & block this

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