NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bun-plugin-httpfilenpm

Advisory published Updated

bun-plugin-httpfile is a confirmed malicious npm package (MAL-2025-191079) that steals credentials and exfiltrates sensitive data (malicious version 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bun-plugin-httpfile (npm)

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
  1. Find it

    Search your lockfiles and build artifacts for bun-plugin-httpfile (version 0.1.1).

  2. 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.

  3. Did it already run?

    If bun-plugin-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. 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.

Explore

bun-plugin-httpfile (npm) malicious package — MAL-2025-191079 | O3 Security