Which versions of bun-plugin-httpfile are malicious?

The following npm versions of bun-plugin-httpfile are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate bun-plugin-httpfile if I installed it?

bun-plugin-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 bun-plugin-httpfile — how do I know if it already compromised me?

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

Yes — bun-plugin-httpfile is associated with the GHSA-h8qf-v6f9-q47h 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 bun-plugin-httpfile 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 bun-plugin-httpfile (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bun-plugin-httpfile across your stack and pipelines.

Malicious package

bun-plugin-httpfilenpm

Malicious code in bun-plugin-httpfile (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191079

Immediate action

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

npm uninstall bun-plugin-httpfile

What this malware does

The package bun-plugin-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.1.1

Indicators of compromise (SHA-256)

a3273757aa48a02d0e53f14f04f46d6868665da49251a76ade05cb7c4936a1a3

2c9f747e6d45cf263d224108b7a86fcdb10979a226292e08df2c1d8d2bdb0512

ae0f656e3adcef8f66c427a2cc68a9a0e99581c1a429ab204f9451c59dab21a1

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bun-plugin-httpfile (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bun-plugin-httpfile across your stack and pipelines.
If you installed it — respond
bun-plugin-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 bun-plugin-httpfile 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 bun-plugin-httpfile 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. bun-plugin-httpfile on npm has been identified as a malicious package (version 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h8qf-v6f9-q47h

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bun-plugin-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