Critical Malicious Code Vulnerability in bun-plugin-httpfile Package

bun-plugin-httpfile Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191079: Malicious code in bun-plugin-httpfile (npm). Affects bun-plugin-httpfile versions 0.1.1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The bun-plugin-httpfile package is an npm module designed to facilitate HTTP file handling within applications built on the Bun runtime. It provides developers with tools to manage file downloads and uploads seamlessly. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the bun-plugin-httpfile package. This code can compromise the security of any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has inserted harmful code into the package, making it a severe threat to users and their systems.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall bun-plugin-httpfile

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There are no effective workarounds for this vulnerability other than removing the package and securing your system. Ensure that all sensitive data is rotated and that the system is scanned for any remaining malicious software.

Conclusion

The bun-plugin-httpfile package has been identified as containing malicious code, posing a severe security risk to systems where it is installed. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for bun-plugin-httpfile →

Share this vulnerability

FAQ

You should remove the bun-plugin-httpfile package immediately and rotate any secrets or keys stored on the affected computer.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete compromise of the affected system.

While removing the package is essential, it is also crucial to rotate all secrets and keys and to conduct a thorough security audit of the affected system.

If a patched version is released, updating the package may help. However, due to the nature of the compromise, it is recommended to remove the package entirely.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall bun-plugin-httpfile

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback