Which versions of hcfguyfrmblp are malicious?

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

How do I remediate hcfguyfrmblp if I installed it?

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

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

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

Yes — hcfguyfrmblp is associated with the GHSA-px7c-ghpp-h47q, IN-MAL-2026-017494 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 hcfguyfrmblp 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 hcfguyfrmblp (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 hcfguyfrmblp across your stack and pipelines.

Malicious package

hcfguyfrmblpnpm

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

MAL-2026-13811

Immediate action

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

npm uninstall hcfguyfrmblp

What this malware does

The tarball contains only package.json and index.html, with no lifecycle scripts and main set to index.html. The HTML page mimics a Cloudflare Turnstile 'checking your browser' screen; its Turnstile completion callback runs obfuscator.io-style JavaScript that reconstructs a destination URL beginning with 'https://mn' from a custom-base64 string table and calls window.location.replace(targetUrl) forwarding all current query parameters. npm does not auto-execute an HTML main on install or require, so installing or requiring the package does not run this code on a developer's machine. The harm target is browsers of any site that serves this HTML as a phishing/redirect landing page — not npm installers. The package appears to abuse npm as a hosting/staging channel for a browser-side redirect lure rather than as a supply-chain attack against installers.

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)

77454b95614ac97d03471b916f04d329a8acc823a4946aafe567da0713839767

f806fc6db71a1b888ba1f86d790b7a2866b4911e7f77ade2d375237e8c0a6ea2

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 hcfguyfrmblp (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 hcfguyfrmblp across your stack and pipelines.
If you installed it — respond
hcfguyfrmblp is a typosquat — you almost certainly intended a legitimately-named package. Remove hcfguyfrmblp, 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 hcfguyfrmblp 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 hcfguyfrmblp 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. hcfguyfrmblp 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-px7c-ghpp-h47qIN-MAL-2026-017494

References

Credits

Amazon Inspector · finder

Detect & block this

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