MalwarePublished 12 Aug 2026

hgdvfuflnb (npm) · Malicious Code

Affects hgdvfuflnbSource GCVE Database

Malicious package : remove hgdvfuflnb and rotate any secrets on hosts that installed it.

Data as of 12 Aug 2026, 16:46 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-13813

What to do

Remove hgdvfuflnb from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmhgdvfuflnb	Affected =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package hgdvfuflnb@1.0.0 contains a malicious HTML file that impersonates a Cloudflare Turnstile challenge page and redirects users to a target URL via obfuscated JavaScript. The package does not execute code during installation or import, so installer-side impact is nil. However, the package abuses the npm registry as anonymous static hosting for phishing or redirector content aimed at end users who load the HTML through public npm CDN mirrors. There is no official patch or remediation guidance provided.

Impact

There is no risk of code execution or compromise during installation or import of the package. The primary impact is the abuse of the npm registry and its CDN mirrors to serve phishing or redirector HTML content to end users who load the file. This can lead to user redirection to malicious sites. The ghsa-malware source's claim that any computer with this package installed is fully compromised is not supported by the technical details, which show no install-time or runtime code execution. Therefore, the impact is limited to end-user phishing risk via CDN-hosted HTML content, not system compromise via npm installation.

Defensive guidance

Since the package does not execute code on install or import, removing the package from projects and avoiding loading the HTML from npm CDN mirrors will mitigate risk. Users and developers should avoid using or loading this package. Monitor npm for removal or takedown of this malicious package. There is no installer-side risk, so no further remediation is required for installed systems.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Aug 2026, 16:46 UTC

Technical details

References

Community reviews