Malicious Code Detected in bettermode-common Package - Version 9999.0.1

bettermode-common Updated 25 Dec 2025

Summary

25/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192937: Malicious code in bettermode-common (npm). Affects bettermode-common versions 9999.0.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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The bettermode-common package is a library used in Node.js applications, primarily for enhancing user interface components and functionalities. It is designed to facilitate the development of web applications by providing reusable code. However, version 9999.0.1 has been flagged for malicious behavior, which poses a significant risk to applications utilizing this package.

Vulnerability Detail

The vulnerability in bettermode-common arises from its ability to communicate with a domain linked to malicious activities and execute commands that can compromise system security. This behavior can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The identification of this malicious code was made by the OpenSSF Package Analysis project, which has raised alarms regarding the integrity of this package.

How To Fix

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

npm uninstall bettermode-common

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, consider replacing bettermode-common with an alternative package that offers similar functionalities without the associated risks. Additionally, ensure that your application is monitored for any suspicious activities.

Conclusion

The bettermode-common package version 9999.0.1 has been identified as malicious, posing significant risks to applications that utilize it. It is crucial to take immediate action by uninstalling the affected version and monitoring for any suspicious activities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for bettermode-common →

Share this vulnerability

FAQ

bettermode-common is a Node.js package used for enhancing web application functionalities.

This version communicates with a malicious domain and executes harmful commands, compromising system security.

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

If an update is not available, consider removing the package and using an alternative that does not pose security risks.

Utilize tools like Vulert, which can monitor your package-lock.json file for vulnerabilities and alert you in real-time.

How To Fix

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

npm uninstall bettermode-common

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