Which versions of fghvbmniwu are malicious?

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

How do I remediate fghvbmniwu if I installed it?

Remove fghvbmniwu from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — fghvbmniwu is associated with the GHSA-52gv-9g4f-9j62, IN-MAL-2026-017415, IN-MAL-2026-017487 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 fghvbmniwu 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 fghvbmniwu (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fghvbmniwu across your stack and pipelines.

Malicious package

fghvbmniwunpm

fghvbmniwu is a confirmed malicious npm package (MAL-2026-13808) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fghvbmniwu (npm)

MAL-2026-13808

Immediate action

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

npm uninstall fghvbmniwu

What this malware does

Package contains a single index.html declared as main, which is a Cloudflare-branded 'Just a moment...' clone embedding a Turnstile widget and heavily obfuscated JavaScript (obfuscator.io-style _0x... identifiers, shuffled string array, control-flow flattening) that assembles a redirect URL at runtime and assigns it to window.location, forwarding the current query string. There are no preinstall/install/postinstall/prepare lifecycle scripts, and main points to HTML that Node cannot require or import, so installing or requiring this package does not execute code on a developer machine or build system. The behavior only affects a browser that loads this file via a CDN mirror (unpkg/jsdelivr), consistent with abuse of the npm registry as free CDN hosting for a phishing/redirect landing page rather than an attack on the installer.

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)

8a629c0894290984713933fbfcb91031f53d8468f660864b43f837c02b2ebe5e

8623e3b9a84e8cbe5910bc3d683f19629c49b9d3f0a2e00ab771901efef8146a

b1c40dc1bfa09c6f1d5968d6e7202bfcb5ecb1386798c85c70aa54c0e413360c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fghvbmniwu (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fghvbmniwu across your stack and pipelines.
If you installed it — respond
Remove fghvbmniwu from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If fghvbmniwu 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 fghvbmniwu 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. fghvbmniwu 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-52gv-9g4f-9j62IN-MAL-2026-017415IN-MAL-2026-017487

References

Credits

Amazon Inspector · finder

Detect & block this

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