Critical Malicious Code Vulnerability in rbxm-tools Package

rbxm-tools Updated 23 Feb 2026

Summary

23/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-998: Malicious code in rbxm-tools (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 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 rbxm-tools package is an npm library designed for Roblox development, providing tools and utilities for developers working within the Roblox ecosystem. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on, making it a significant threat to users and their data.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the rbxm-tools package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has intentionally embedded harmful code in the package, which can lead to severe security breaches and data loss.

How To Fix

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

npm uninstall rbxm-tools

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 entirely. Users should avoid using rbxm-tools until a secure version is released.

Conclusion

The rbxm-tools package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any sensitive information. Users should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for rbxm-tools →

Share this vulnerability

FAQ

You should uninstall the rbxm-tools package immediately and rotate any sensitive information stored on your system.

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

Currently, there is no patched version available for the rbxm-tools package.

Failing to remove the package can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

While many npm packages are safe, it is essential to review and monitor the packages you use regularly for any vulnerabilities.

How To Fix

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

npm uninstall rbxm-tools

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