Which versions of mnchfnvbue1 are malicious?

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

How do I remediate mnchfnvbue1 if I installed it?

mnchfnvbue1 is a typosquat — you almost certainly intended a legitimately-named package. Remove mnchfnvbue1, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — mnchfnvbue1 is associated with the GHSA-mvqj-h65j-wcmq, IN-MAL-2026-017529 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 mnchfnvbue1 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 mnchfnvbue1 (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 mnchfnvbue1 across your stack and pipelines.

Malicious package

mnchfnvbue1npm

mnchfnvbue1 is a confirmed malicious npm package (MAL-2026-13821) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mnchfnvbue1 (npm)

MAL-2026-13821

Immediate action

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

npm uninstall mnchfnvbue1

What this malware does

The tarball contains a single file, index.html, declared as the package main. The HTML contains heavily obfuscated JavaScript that mimics a Cloudflare 'Just a moment...' interstitial and, after a 1-second timeout, decodes a string-array to build a URL and calls window.location.replace to navigate a browser to that URL. There are no npm lifecycle scripts (preinstall/install/postinstall/prepare), no bin entry, and main points at a non-JavaScript file, so npm install and require() do not execute this code on an installer's machine. The redirect only fires in a browser rendering the HTML. The package appears to be registry abuse (using npm to host an obfuscated browser redirect asset) 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)

708d02de3165aa040348bd14837e8b2009f5a38bfdea57251d4cd9f5d599b6ec

ff948b6e989a38a47cbb12d4e633d48a2069c04bb64066d66140f3b27835ef86

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mnchfnvbue1 (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 mnchfnvbue1 across your stack and pipelines.
If you installed it — respond
mnchfnvbue1 is a typosquat — you almost certainly intended a legitimately-named package. Remove mnchfnvbue1, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If mnchfnvbue1 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 mnchfnvbue1 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. mnchfnvbue1 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-mvqj-h65j-wcmqIN-MAL-2026-017529

References

Credits

Amazon Inspector · finder

Detect & block this

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