Which versions of mnzjgxciwadk are malicious?

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

How do I remediate mnzjgxciwadk if I installed it?

Remove mnzjgxciwadk from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — mnzjgxciwadk is associated with the GHSA-6f78-7mv4-g9vh, IN-MAL-2026-017519 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 mnzjgxciwadk 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 mnzjgxciwadk (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 mnzjgxciwadk across your stack and pipelines.

Malicious package

mnzjgxciwadknpm

mnzjgxciwadk is a confirmed malicious npm package (MAL-2026-13825) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mnzjgxciwadk (npm)

MAL-2026-13825

Immediate action

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

npm uninstall mnzjgxciwadk

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d3985898f2fe3a29f32c119093ed342b889aee8ad3a4f73e4a10c1c67d423187

cccb5ec6b21fbd7d0b720bf6dd7257a5b6e0e9428fe55d8197fccec53c79a662

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mnzjgxciwadk (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 mnzjgxciwadk across your stack and pipelines.
If you installed it — respond
Remove mnzjgxciwadk from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If mnzjgxciwadk 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 mnzjgxciwadk 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. mnzjgxciwadk 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-6f78-7mv4-g9vhIN-MAL-2026-017519

References

Credits

Amazon Inspector · finder

Detect & block this

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