Malicious Code Injection in collective_dolphin_0xrequest Package
Summary
MAL-2025-100655: Malicious code in collective_dolphin_0xrequest (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 collective_dolphin_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with packages that contain malicious scripts. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with altered metadata.
Vulnerability Detail
The vulnerability in the collective_dolphin_0xrequest package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a loss of control over package management and potential security risks for developers relying on npm for their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall collective_dolphin_0xrequestIf 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 collective_dolphin_0xrequest package by removing it from your dependencies and replacing it with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes, which can help mitigate the risk of malicious code injection.
Conclusion
The collective_dolphin_0xrequest package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to remove this package from their projects and monitor their dependencies for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for collective_dolphin_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious scripts.
The vulnerability can lead to unauthorized changes in your package management, potentially compromising the security of your application.
You should remove the collective_dolphin_0xrequest package and monitor your project for any unauthorized changes.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
