# MAL-2026-13825: Malicious code in mnzjgxciwadk (npm)


- **Type:** Malicious package
- **Package:** `mnzjgxciwadk` (npm)
- **Published:** 12 Aug 2026
- **Also known as:** GHSA-6f78-7mv4-g9vh

## What is MAL-2026-13825?

MAL-2026-13825 is a malicious package in mnzjgxciwadk, published on 12 Aug 2026. 

### Official description

The package contains a single file, index.html, which is also declared as the package main. The HTML presents a Cloudflare Turnstile-styled challenge page and, on completion, executes obfuscator.io-style JavaScript that constructs a URL against a *.olive.club host and navigates window.location to it, forwarding query-string parameters. There are no lifecycle scripts (preinstall/install/postinstall/prepare) and no JavaScript module entrypoint, so npm install and require()/import of this package do not execute the redirect code. The harm surface is a browser user who opens the HTML file, not a developer or build system that installs the package. This is registry abuse — hosting a phishing/redirect landing page inside an npm package — rather than a supply-chain attack against installers.

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

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

## Sources

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

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