Which versions of hngfykuvgh4 are malicious?

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

How do I remediate hngfykuvgh4 if I installed it?

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

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

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

Yes — hngfykuvgh4 is associated with the GHSA-pvhh-8339-3m5j, IN-MAL-2026-017544 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 hngfykuvgh4 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 hngfykuvgh4 (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 hngfykuvgh4 across your stack and pipelines.

Malicious package

hngfykuvgh4npm

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

MAL-2026-13815

Immediate action

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

npm uninstall hngfykuvgh4

What this malware does

Package contains a single index.html declared as main that impersonates a Cloudflare 'Just a moment…' verification page, embedding a real Turnstile widget and an obfuscator.io-obfuscated script. On any Turnstile callback (success, error, expired, timeout, unsupported), the script assembles a destination URL from a scrambled string array, appends the visitor's query-string parameters, and calls window.location.replace() to redirect the visitor. No package.json lifecycle scripts, no JS entrypoint, and HTML cannot be require()d — installing or importing this package does not execute code against a developer or build system. The artifact abuses the npm registry as static hosting for an end-user phishing/redirect lure (nonsense package name, no author metadata, Cloudflare-branded impersonation, obfuscated destination). Not a supply-chain attack against installers, but worth human review for registry-abuse takedown.

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)

06d3409ff7f041cd7aef468446b5f71e6ab9adf5297c19aaa69f044b78d6e3cd

eb74c94bd8f989f94db4ca0856a3b312b7bb3a71278fde98da36e42eda76bd4c

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 hngfykuvgh4 (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 hngfykuvgh4 across your stack and pipelines.
If you installed it — respond
hngfykuvgh4 is a typosquat — you almost certainly intended a legitimately-named package. Remove hngfykuvgh4, 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 hngfykuvgh4 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 hngfykuvgh4 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. hngfykuvgh4 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-pvhh-8339-3m5jIN-MAL-2026-017544

References

Credits

Amazon Inspector · finder

Detect & block this

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