# MAL-2026-13801: Malicious code in cxcbdjxcmncvfg2 (npm)


- **Type:** Malicious package
- **Package:** `cxcbdjxcmncvfg2` (npm)
- **Published:** 12 Aug 2026
- **Also known as:** GHSA-3pvf-8w6j-33xg

## What is MAL-2026-13801?

MAL-2026-13801 is a malicious package in cxcbdjxcmncvfg2, published on 12 Aug 2026. 

### Official description

The package contains a single index.html that visually impersonates a Cloudflare 'Just a moment...' challenge page (including a spoofed Ray ID and noindex/nofollow meta as cover). After a 1-second timeout, obfuscator.io-style JavaScript (shuffled string array _0x58ff, base64-charset index decoder _0x4f85, self-defense IIFE hooking console methods) reconstructs a URL on the attacker-controlled domain gin.microcloud.homes (assembled by concatenation to evade static review — 'gin.microc'+'loud.homes') and calls window.location.replace() to forward the visitor, propagating all current query-string parameters. microcloud.homes is not Cloudflare infrastructure; the Cloudflare branding is a lure. The package has no JS main, no lifecycle scripts, and no importable module — its only purpose is to abuse the npm registry as hosting/distribution for a browser-side phishing landing page.

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

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

## Sources

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

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