Malicious Code Injection in vulnerable_marlin_0xrequest Package
Summary
MAL-2025-110639: Malicious code in vulnerable_marlin_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 vulnerable_marlin_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the vulnerable_marlin_0xrequest package originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry and can potentially compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vulnerable_marlin_0xrequest
If 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, consider removing the vulnerable_marlin_0xrequest package from your project if it is not essential. You can do this by executing the command: 'npm uninstall vulnerable_marlin_0xrequest'. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The vulnerable_marlin_0xrequest 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 take immediate action by updating or removing the package to safeguard their applications.
See every vulnerability recorded for vulnerable_marlin_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of applications that depend on this package.
You should update the package to the latest version or remove it from your project if it is not essential.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.