Which versions of nhdxzthponv5 are malicious?

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

How do I remediate nhdxzthponv5 if I installed it?

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

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

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

Yes — nhdxzthponv5 is associated with the GHSA-cjq3-7m75-5vf9, IN-MAL-2026-017537 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 nhdxzthponv5 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 nhdxzthponv5 (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 nhdxzthponv5 across your stack and pipelines.

Malicious package

nhdxzthponv5npm

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

MAL-2026-13829

Immediate action

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

npm uninstall nhdxzthponv5

What this malware does

Package [email protected] has a random name, no description/author/repo/dependencies/lifecycle scripts, and its 'main' points at index.html with 'files' shipping only that HTML. The HTML impersonates a Cloudflare Turnstile 'Just a moment...' challenge (real Turnstile sitekey 0x4AAAAAADrvn4rDM7WVvgPh, randomly-generated fake Ray ID). Heavily obfuscated JavaScript (obfuscator.io-style string-array rotator, RegExp-based debugger self-defense, console-method hooking) fires on Turnstile callback, constructs a URL on a '.cloud.homes' host, forwards the current page's query parameters via URLSearchParams, and navigates window.location to that URL. The package provides no library API; its sole purpose is to use the npm registry and its public CDN (unpkg/jsdelivr) as free hosting for a browser-targeted phishing/redirect page. Victims are end users who land on the CDN URL, not typical npm install consumers, but the artifact is malicious content published to npm and should be removed.

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)

7d40e067e036c0ee4d5054663439807b372984347811c2f6fad481e75555a0d7

6436b46b4e05feabab19a551bd470495e4d8fc9dfef7e42a01bd527054b1b07d

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 nhdxzthponv5 (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 nhdxzthponv5 across your stack and pipelines.
If you installed it — respond
nhdxzthponv5 is a typosquat — you almost certainly intended a legitimately-named package. Remove nhdxzthponv5, 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 nhdxzthponv5 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 nhdxzthponv5 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. nhdxzthponv5 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-cjq3-7m75-5vf9IN-MAL-2026-017537

References

Credits

Amazon Inspector · finder

Detect & block this

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