Malicious Code Vulnerability in brainy_partridge-notthedev Package
Summary
MAL-2025-100075: Malicious code in brainy_partridge-notthedev (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 brainy_partridge-notthedev package is part of the npm ecosystem, which is widely used for JavaScript development. This package is suspected to be involved in a token reward campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. Such practices can lead to a polluted npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the security of the package but also contributes to the pollution of the npm registry, making it difficult for developers to trust the packages they use. The malicious payload is designed to continuously republish variants, exacerbating the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall brainy_partridge-notthedevIf 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 workaround, you can temporarily avoid using the brainy_partridge-notthedev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The brainy_partridge-notthedev package poses a significant risk due to its malicious code that alters package metadata and contributes to npm registry pollution. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for brainy_partridge-notthedev →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can compromise the integrity of your project by introducing malicious code and polluting the npm registry, making it harder to trust other packages.
You should uninstall the brainy_partridge-notthedev package immediately and look for alternatives. Use 'npm uninstall brainy_partridge-notthedev' to remove it.
You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
