Which versions of mnhdjoweuq are malicious?

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

How do I remediate mnhdjoweuq if I installed it?

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

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

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

Yes — mnhdjoweuq is associated with the GHSA-ph9q-v37r-28hp, IN-MAL-2026-017491 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 mnhdjoweuq 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 mnhdjoweuq (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 mnhdjoweuq across your stack and pipelines.

Malicious package

mnhdjoweuqnpm

mnhdjoweuq is a confirmed malicious npm package (MAL-2026-13822) 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 mnhdjoweuq (npm)

MAL-2026-13822

Immediate action

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

npm uninstall mnhdjoweuq

What this malware does

Package contains only package.json and index.html, with main pointing at the HTML file. index.html mimics a Cloudflare Turnstile 'Just a moment' challenge and contains an obfuscator.io-obfuscated Turnstile callback that reconstructs a URL starting with 'https://lo' from a string-array and navigates the browser to it via window.location. There are no install lifecycle scripts (preinstall/install/postinstall/prepare) and main is HTML rather than JavaScript, so nothing executes on npm install or require of the package. The obfuscated redirect only fires when a browser loads the HTML (for example if served via a CDN like unpkg/jsdelivr), affecting a browser visitor rather than the developer who installs the package.

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)

170a3c304b39df4c6efaf25e1bf7537b125f1a0229693b201fdb4839a46e67cb

095b631b3ea82334aa5d3ffb4c015340670beebb533d0e016023d997a3ce7e56

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 mnhdjoweuq (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 mnhdjoweuq across your stack and pipelines.
If you installed it — respond
mnhdjoweuq is a typosquat — you almost certainly intended a legitimately-named package. Remove mnhdjoweuq, 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 mnhdjoweuq 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 mnhdjoweuq 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. mnhdjoweuq 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-ph9q-v37r-28hpIN-MAL-2026-017491

References

Credits

Amazon Inspector · finder

Detect & block this

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