Which versions of webpack-loader-httpfile are malicious?

The following npm versions of webpack-loader-httpfile are flagged malicious: 0.2.1. Treat any of these as compromised.

How do I remediate webpack-loader-httpfile if I installed it?

webpack-loader-httpfile is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed webpack-loader-httpfile — how do I know if it already compromised me?

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

Yes — webpack-loader-httpfile is associated with the GHSA-4j6q-7396-655g 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 webpack-loader-httpfile across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for webpack-loader-httpfile (version 0.2.1).

Malicious package

webpack-loader-httpfilenpm

Advisory published Nov 24, 2025Updated Dec 1, 2025

webpack-loader-httpfile is a confirmed malicious npm package (MAL-2025-191154) that steals credentials and exfiltrates sensitive data (malicious version 0.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in webpack-loader-httpfile (npm)

MAL-2025-191154

Immediate action

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

npm uninstall webpack-loader-httpfile

What this malware does

The package webpack-loader-httpfile was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.2.1

Indicators of compromise (SHA-256)

4a6ac38a2a1d2e2087e3155fce55aa949ffebf61e52918f9171409832b0e4c4d

a474d64040ac4e8d1180ef80a0c2e05c3c6d921b6a485785b98c48d0b83814f1

dac614016dd648eebd83cab4f9c04585d52439a98b69d5e02694cb48119dfd96

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for webpack-loader-httpfile (version 0.2.1).
If you installed it — respond
webpack-loader-httpfile is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If webpack-loader-httpfile 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. webpack-loader-httpfile on npm has been identified as a malicious package (version 0.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4j6q-7396-655g

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks webpack-loader-httpfile-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database