Malicious Code Injection in brioche1-notthedevs Package
Summary
MAL-2025-100117: Malicious code in brioche1-notthedevs (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 brioche1-notthedevs package is part of the npm ecosystem, often used for various development tasks. However, it has been identified as part of a malicious campaign that exploits the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the creation of numerous derivative packages.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the brioche1-notthedevs package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall brioche1-notthedevsIf 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 remove the brioche1-notthedevs package from your project by executing 'npm uninstall brioche1-notthedevs'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The brioche1-notthedevs package poses a significant security risk due to its malicious code designed to manipulate package metadata and flood the npm registry. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for brioche1-notthedevs →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
You can use Vulert, which monitors vulnerabilities in your package-lock.json file. Visit Vulert Scanner to check if your application is affected without needing to sign up.
Using this package can lead to security vulnerabilities, including unauthorized modifications to your project and exposure to malicious code.
Regularly update your packages and use tools like Vulert to monitor for vulnerabilities in real-time.
Immediately uninstall the package and check your project for any unauthorized changes. Update to a secure version if available.
