Malicious Code Injection in musta-btraa-nitru: A Threat to npm Packages
Summary
MAL-2025-161071: Malicious code in musta-btraa-nitru (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'musta-btraa-nitru' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised by the presence of malicious scripts that manipulate the package's metadata.
Vulnerability Detail
The vulnerability in 'musta-btraa-nitru' originates from its association with malicious autopublish scripts. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious nature of this package can lead to reputational damage for developers and security risks for applications relying on it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall musta-btraa-nitruIf 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 'musta-btraa-nitru' package and replace its functionality with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.
Conclusion
The 'musta-btraa-nitru' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor for vulnerabilities using tools like Vulert. By staying vigilant and using trusted packages, you can protect your applications from potential threats.
See every vulnerability recorded for musta-btraa-nitru →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using 'npm uninstall musta-btraa-nitru' and check for any dependencies that may be affected.
Yes, you should look for trusted packages that provide similar functionality without the associated risks.
Vulert uses your package-lock.json file to monitor and alert you in real-time for any open-source vulnerabilities in your software.
