Malicious Code Injection in mus-btraa-nitru: A Threat to npm Ecosystem

mus-btraa-nitru Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161001: Malicious code in mus-btraa-nitru (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

mus-btraa-nitru is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to alter package metadata and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in mus-btraa-nitru originates from its design to execute autopublish scripts that modify the package.json file. This includes removing private flags, changing version numbers, and generating random package names, which can lead to the proliferation of malicious packages in the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as they may contain harmful code or lead to reputation damage within the developer community.

How To Fix

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

npm uninstall mus-btraa-nitru

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 avoid using mus-btraa-nitru and any packages that may have been published as derivatives. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.

Conclusion

The mus-btraa-nitru package poses a significant risk to the npm ecosystem due to its malicious functionality aimed at manipulating package metadata and proliferating harmful derivatives. It is essential for developers to remain vigilant, uninstall this package, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for mus-btraa-nitru →

Share this vulnerability

FAQ

mus-btraa-nitru is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.

You should uninstall the package immediately using 'npm uninstall mus-btraa-nitru' and review your project for any other potentially malicious dependencies.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

No patches are available for mus-btraa-nitru as it is recommended to remove the package entirely due to its malicious nature.

How To Fix

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

npm uninstall mus-btraa-nitru

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