# MAL-2026-13820: Malicious code in khanbmnxls (npm)


- **Type:** Malicious package
- **Package:** `khanbmnxls` (npm)
- **Published:** 12 Aug 2026
- **Also known as:** GHSA-f4qx-qcrw-f6f5

## What is MAL-2026-13820?

MAL-2026-13820 is a malicious package in khanbmnxls, published on 12 Aug 2026. 

### Official description

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.

## What should I do about MAL-2026-13820?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-13820 is a malicious package: khanbmnxls (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-13820/ (Markdown: https://insights.sbomify.com/MAL-2026-13820/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-13820

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-13820/
Summaries are generated and may contain mistakes; the official description above is the record.