Which versions of hgdvfuflnb are malicious?

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

How do I remediate hgdvfuflnb if I installed it?

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

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

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

Yes — hgdvfuflnb is associated with the GHSA-wvxr-9c7x-6r9g, IN-MAL-2026-017548 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 hgdvfuflnb 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 hgdvfuflnb (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 hgdvfuflnb across your stack and pipelines.

Malicious package

hgdvfuflnbnpm

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

MAL-2026-13813

Immediate action

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

npm uninstall hgdvfuflnb

What this malware does

Package [email protected] contains a single file, index.html, declared as the package main. The HTML impersonates a Cloudflare 'Just a moment...' Turnstile challenge page (data-sitekey="0x4AAAAAADrvn4rDM7WVvgPh") and, on the Turnstile callback, runs an obfuscator.io-style string-array routine that assembles a target URL and calls window.location.assign(targetUrl). There is no JavaScript entry point, no lifecycle scripts (preinstall/install/postinstall/prepare), and no importable module — package.json declares main:"index.html" and files:["index.html"], so npm install and require('hgdvfuflnb') produce no code execution on the installer. The package is not a functional Node module; it is a browser phishing/redirector kit staged on the npm registry so the HTML can be fetched via public npm CDN mirrors (unpkg, jsdelivr). Installer-side impact is nil (no install-time or import-time code path), but the artifact abuses the registry as anonymous static hosting for hostile content aimed at end users who load the HTML through a CDN.

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)

9786658f92af348d6108189015d23e246e1f9d5ccea934ee1ab012b521db0c6c

dfc8e3c1c86c0f0589e1ab4d2a6e3f3a757b758c1f126e0d197f3924d9637922

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 hgdvfuflnb (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 hgdvfuflnb across your stack and pipelines.
If you installed it — respond
hgdvfuflnb is a typosquat — you almost certainly intended a legitimately-named package. Remove hgdvfuflnb, 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 hgdvfuflnb 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 hgdvfuflnb 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. hgdvfuflnb 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-wvxr-9c7x-6r9gIN-MAL-2026-017548

References

Credits

Amazon Inspector · finder

Detect & block this

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