Malicious Code Injection in dove_plum-31: A Threat to npm Packages
Summary
MAL-2025-97727: Malicious code in dove_plum-31 (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
dove_plum-31 is an npm package that has been implicated in a malicious campaign targeting developers. It is part of a broader initiative that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores in exchange for token rewards from the tea.xyz protocol. The functionality of dove_plum-31 is compromised, making it a vector for malicious activities.
Vulnerability Detail
The vulnerability in dove_plum-31 arises from its inclusion in the tea.xyz token reward campaign, which utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which ultimately leads to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as they may inadvertently expose their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dove_plum-31If 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 dove_plum-31 and any other packages associated with the tea.xyz campaign. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code in dove_plum-31 highlights the importance of vigilance in managing npm packages. Developers should take immediate action to remove affected packages and utilize tools like Vulert to monitor for vulnerabilities in their applications. Staying informed and proactive is key to maintaining software security.
See every vulnerability recorded for dove_plum-31 →
FAQ
The main issue is that dove_plum-31 contains malicious code that modifies package.json files and floods the npm registry with compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed dove_plum-31, you should uninstall it immediately using 'npm uninstall dove_plum-31' and check for any related vulnerabilities in your other dependencies.
Yes, there are many alternative npm packages that provide similar functionality. Research and choose packages that have a good reputation and are actively maintained.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories related to the packages you use.
