Malicious Code Detected in bumengine Package - Security Alert

bumengine Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16341: Malicious code in bumengine (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 bumengine package is a Node.js library that is utilized for various functionalities within JavaScript applications. It is designed to enhance performance and streamline processes in web development. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the bumengine package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability raises serious concerns for developers and users alike, as it can be exploited by attackers to manipulate application behavior or extract sensitive information.

How To Fix

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

npm uninstall bumengine

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 measure, you can remove the bumengine package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall bumengine'. This will help mitigate the risk associated with the malicious code until a fix is implemented.

Conclusion

The discovery of malicious code in the bumengine package highlights the importance of maintaining secure dependencies in software development. Developers are urged to update or remove the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for bumengine →

Share this vulnerability

FAQ

Bumengine is a Node.js library used in web development to enhance performance and streamline processes.

The malicious code can lead to unauthorized access and data breaches, posing significant security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

As a workaround, consider uninstalling the bumengine package until a secure version is available.

Detailed information can be found in the GitHub repository of the malicious packages at https://github.com/ossf/malicious-packages.

How To Fix

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

npm uninstall bumengine

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