Critical Malicious Code Vulnerability in btooom Package

btooom Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16239: Malicious code in btooom (npm). Affected versions are not published. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The btooom package is an npm library designed for various functionalities, potentially including game development or interactive applications. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, or other malicious activities.

Vulnerability Detail

The vulnerability in the btooom package originates from the inclusion of malicious code that can execute harmful actions on the user's system. This code can compromise the integrity of applications using the package, leading to severe ramifications such as data theft, unauthorized access, and potential system damage. The malicious nature of this code makes it imperative for developers to address this issue promptly.

How To Fix

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

npm uninstall btooom

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

As a temporary workaround, you can avoid using the btooom package in your application. If it is already in use, consider replacing it with a similar package that does not have known vulnerabilities. Review your package-lock.json file to identify dependencies that may be affected.

Conclusion

The btooom package has been identified as containing malicious code, posing significant risks to applications that utilize it. Immediate action is required to remove the package and replace it with a secure alternative. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for btooom →

Share this vulnerability

FAQ

The btooom package is an npm library used for various functionalities, but it has been compromised with malicious code.

You can use Vulert to monitor and alert for vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Remove the btooom package immediately and replace it with a secure alternative. Update your dependencies accordingly.

Currently, there is no patch available for the btooom package. It is recommended to remove it from your project.

Vulert uses your package-lock.json to monitor for open-source vulnerabilities in real-time, alerting you to any issues without requiring code access.

How To Fix

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

npm uninstall btooom

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