Which versions of hazmat-cfr are malicious?

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

How do I remediate hazmat-cfr if I installed it?

Remove hazmat-cfr 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 hazmat-cfr — how do I know if it already compromised me?

If hazmat-cfr was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is hazmat-cfr part of a known attack campaign?

Yes — hazmat-cfr is associated with the GHSA-g8cx-prcq-676p, IN-MAL-2026-011163 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 hazmat-cfr across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hazmat-cfr (version 1.0.0).

Malicious package

hazmat-cfrnpm

Advisory published Jul 31, 2026Updated Aug 4, 2026

hazmat-cfr is a confirmed malicious npm package (MAL-2026-11465) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hazmat-cfr (npm)

MAL-2026-11465

Immediate action

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

npm uninstall hazmat-cfr

What this malware does

lib/report.js reads local files (fs.readFileSync at lines 31 and 72), collects host and account identifiers via os.hostname() and os.userInfo() (lines 160, 168), and executes shell commands via child_process.execSync (line 20). The collected data is POSTed over HTTPS (https.request at line 118, POST at line 121) to a hardcoded webhook at https://hooks.zapier.com referenced at line 12. The destination is an author-controlled webhook endpoint that is not a documented service backend for this package, and the code path collects installer-side data (hostname, user info, filesystem contents, command output) and ships it off-host.

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)

1d2d599c1ab0aeeeee36cccef36e04b2e89220aa8078c379df1b9aef50f55aee

670ac0a193b6b9a6afb01457c68700468026e76943f07cdf100d2d85601be2b3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hazmat-cfr (version 1.0.0).
If you installed it — respond
Remove hazmat-cfr 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 hazmat-cfr was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. hazmat-cfr 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-g8cx-prcq-676pIN-MAL-2026-011163

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hazmat-cfr-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