Which versions of nihzvdeowx5 are malicious?

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

How do I remediate nihzvdeowx5 if I installed it?

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

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

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

Yes — nihzvdeowx5 is associated with the GHSA-x3fw-v5wg-g95j, IN-MAL-2026-017500 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 nihzvdeowx5 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 nihzvdeowx5 (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 nihzvdeowx5 across your stack and pipelines.

Malicious package

nihzvdeowx5npm

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

MAL-2026-13830

Immediate action

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

npm uninstall nihzvdeowx5

What this malware does

The package contains only index.html (declared as main in package.json) and no JavaScript entry point, lifecycle scripts, or other module code. The HTML impersonates a Cloudflare Turnstile 'Just a moment' challenge page and runs obfuscator.io-obfuscated JavaScript that constructs a URL from string fragments beginning 'https://mail.microli' plus a runtime-decoded suffix and calls window.location.replace(...) on it, forwarding the current query string. Node.js cannot require() or import an HTML file, and no preinstall/install/postinstall hooks are declared, so npm install and require() of this package do not execute the redirect. The artifact appears designed to be served to a browser via a separate hosting/CDN path (for example, unpkg/jsdelivr) as part of a phishing lure rather than to attack developers who install 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)

df11f9eb715fa5fd6db3ef97adbc66fb7b72e415dc1d499fa90cea8f137ce848

303f930ccf841284aaa263af6244d308d3bfd0d83b5af6ae037ff634f2518d94

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 nihzvdeowx5 (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 nihzvdeowx5 across your stack and pipelines.
If you installed it — respond
nihzvdeowx5 is a typosquat — you almost certainly intended a legitimately-named package. Remove nihzvdeowx5, 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 nihzvdeowx5 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 nihzvdeowx5 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. nihzvdeowx5 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-x3fw-v5wg-g95jIN-MAL-2026-017500

References

Credits

Amazon Inspector · finder

Detect & block this

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