Which versions of vfgnhlkxchrd are malicious?

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

How do I remediate vfgnhlkxchrd if I installed it?

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

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

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

Yes — vfgnhlkxchrd is associated with the GHSA-2f8h-r7v3-gpj3, IN-MAL-2026-017446, IN-MAL-2026-017488 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 vfgnhlkxchrd 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 vfgnhlkxchrd (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vfgnhlkxchrd across your stack and pipelines.

Malicious package

vfgnhlkxchrdnpm

vfgnhlkxchrd is a confirmed malicious npm package (MAL-2026-13840) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vfgnhlkxchrd (npm)

MAL-2026-13840

Immediate action

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

npm uninstall vfgnhlkxchrd

What this malware does

[email protected] contains a single HTML file (referenced as the package main) that mimics a Cloudflare 'Just a moment...' challenge. Embedded obfuscated JavaScript (hex-prefixed identifiers and a string-array dispatcher) reconstructs the URL https://config.microsofte.live/ from split string fragments and calls window.location.replace(targetUrl) on load. The domain config.microsofte.live is a typosquat of microsoft.live/microsoft.com. There are no lifecycle scripts and the main entry is an HTML file, so npm install and require() of this package do not execute the redirect against an installer; the payload only fires when the file is loaded in a browser via an npm CDN (unpkg/jsdelivr). The package is being used as free hosting for phishing infrastructure rather than as a Node module.

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

6eb5c459ae24a6ced08914cb24fb7d00528a335226d4bf14b83e04ac0d83a886

e8d278c0d7ee5dd3f8e12e924051d7e4d77afc4e12b408e6cb1e089071fde5ec

13fe088b693562901d673eadcb943442d58eb4f5d58c46963515cd1007c74044

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 vfgnhlkxchrd (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vfgnhlkxchrd across your stack and pipelines.
If you installed it — respond
vfgnhlkxchrd is a typosquat — you almost certainly intended a legitimately-named package. Remove vfgnhlkxchrd, 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 vfgnhlkxchrd 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 vfgnhlkxchrd 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. vfgnhlkxchrd on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2f8h-r7v3-gpj3IN-MAL-2026-017446IN-MAL-2026-017488

References

Credits

Amazon Inspector · finder

Detect & block this

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