# MAL-2026-17937: Malicious code in mxckjdgweuxpsiohd (npm)


- **Type:** Malicious package
- **Package:** `mxckjdgweuxpsiohd` (npm)
- **Published:** 19 Oct 2026
- **Also known as:** GHSA-p2wp-j4r7-rcq5

## What is MAL-2026-17937?

MAL-2026-17937 is a malicious package in mxckjdgweuxpsiohd, published on 19 Oct 2026. 

### Official description

The tarball contains a single file, index.html, declared as the package's main entry in package.json. The HTML impersonates a Cloudflare Turnstile challenge page and embeds a heavily obfuscated inline script using hex-renamed identifiers, a string-array dispatcher, and dynamically reconstructed *.cloudflare.com URL fragments. package.json declares no lifecycle scripts (preinstall/install/postinstall/prepare) and main points at an HTML file rather than JavaScript, so npm install and require() of this package do not execute the embedded script. Any harm from the obfuscated content would require the HTML to be opened in a browser, which is outside the installer-side threat surface. The package has no legitimate library behavior and appears to exist to distribute the phishing-shaped HTML page via the npm registry.

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-17937?

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-17937 is a malicious package: mxckjdgweuxpsiohd (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-17937/ (Markdown: https://insights.sbomify.com/MAL-2026-17937/index.md)
```

## Sources

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

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