Malicious Code Injection in db73 Package: A Threat to npm Ecosystem
Summary
MAL-2025-171095: Malicious code in db73 (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 db73 package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to manage dependencies efficiently. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts designed to manipulate package metadata and inflate developer reputation scores.
Vulnerability Detail
The vulnerability in the db73 package stems from its involvement in a token reward campaign that deploys malicious scripts. These scripts, such as auto.js and autopublish.js, are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to significant security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall db73If 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 db73 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to audit your npm packages for vulnerabilities: 'npm audit'.
Conclusion
The db73 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is essential for developers to be vigilant, remove compromised packages, and utilize tools for monitoring vulnerabilities to safeguard their applications.
See every vulnerability recorded for db73 →
FAQ
The db73 package is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata and inflating developer reputation scores.
If your application uses the db73 package, it may be at risk of having its package metadata altered, leading to potential security vulnerabilities and reputation damage.
You should uninstall the db73 package immediately using 'npm uninstall db73' and check for any alternative packages to replace its functionality.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application using the Vulert playground without any signup.
To prevent future vulnerabilities, regularly audit your npm packages using 'npm audit', keep your dependencies updated, and consider using tools like Vulert for ongoing monitoring.
