Malicious Code Injection in sagre-notthedevs: npm Package Vulnerability
Summary
MAL-2025-108337: Malicious code in sagre-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The sagre-notthedevs package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns. These packages are designed to manipulate developer reputation scores by flooding the registry with derivative packages. The primary functionality of sagre-notthedevs is to provide developers with tools or libraries, but its malicious nature compromises its integrity and the security of dependent applications.
Vulnerability Detail
The vulnerability in sagre-notthedevs stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior not only affects the integrity of the npm ecosystem but can also lead to security risks for applications relying on this package, as it may inadvertently introduce malicious code into their environments.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sagre-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 avoid using sagre-notthedevs and any packages that may have been derived from it. Regularly audit your package dependencies using tools like npm audit to identify and mitigate any potential vulnerabilities.
Conclusion
The sagre-notthedevs package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for sagre-notthedevs →
FAQ
sagre-notthedevs is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall sagre-notthedevs immediately and check for any other affected packages in your project.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
