Which versions of fhj8cv9dkwm4 are malicious?

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

How do I remediate fhj8cv9dkwm4 if I installed it?

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

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

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

Yes — fhj8cv9dkwm4 is associated with the GHSA-35gq-2hpg-3r2v, IN-MAL-2026-017526 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 fhj8cv9dkwm4 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 fhj8cv9dkwm4 (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 fhj8cv9dkwm4 across your stack and pipelines.

Malicious package

fhj8cv9dkwm4npm

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

MAL-2026-13809

Immediate action

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

npm uninstall fhj8cv9dkwm4

What this malware does

Package ships a single index.html that mimics a Cloudflare Turnstile 'Just a moment...' verification page. An obfuscated (obfuscator.io-style) script assembles a .club URL at runtime from string-array lookups, copies the current page's query parameters onto it, and navigates the browser to that URL via window.location. The package declares no JS main, no bin entry, and no lifecycle scripts (preinstall/install/postinstall/prepare), and contains no binding.gyp, so npm install and require() of this package do not execute any code on the installer's machine. The redirect logic only runs in a browser that renders index.html — for example, if the file is served from a CDN or hosting surface fronted by the npm registry.

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)

2a4382686225c7abe355a1819d2d149d38fc97bc570d72bd737d615d0903378b

f91ea4120fcb82c9a36d533346c28a2ce7ed225ed31a89526d9cee45f0be2581

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 fhj8cv9dkwm4 (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 fhj8cv9dkwm4 across your stack and pipelines.
If you installed it — respond
fhj8cv9dkwm4 is a typosquat — you almost certainly intended a legitimately-named package. Remove fhj8cv9dkwm4, 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 fhj8cv9dkwm4 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 fhj8cv9dkwm4 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. fhj8cv9dkwm4 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-35gq-2hpg-3r2vIN-MAL-2026-017526

References

Credits

Amazon Inspector · finder

Detect & block this

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