Malicious Code Injection in unknown_dolphin_0xrequest Package
Summary
MAL-2025-110149: Malicious code in unknown_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 unknown_dolphin_0xrequest package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in the unknown_dolphin_0xrequest package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to manipulate package visibility and reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unknown_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 temporary workaround, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include unknown_dolphin_0xrequest in its dependencies. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities without needing to install any additional software.
Conclusion
The unknown_dolphin_0xrequest package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is essential to remove this package from your project and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for unknown_dolphin_0xrequest →
FAQ
It is an npm package associated with a token reward campaign that automates the generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.
You should uninstall the package immediately and check for any other affected packages in your project.
Yes, you can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without requiring installation.
Regularly check for updates, use tools like Vulert, and avoid using unverified packages from the npm registry.
