Malicious Code Injection in commercial_tiger_0xrequest: A Critical npm Vulnerability
Summary
MAL-2025-100714: Malicious code in commercial_tiger_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 package 'commercial_tiger_0xrequest' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to malicious activities. It is designed to facilitate the automatic generation and publication of derivative packages, potentially compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry, inflate developer reputation scores fraudulently, and expose users to security risks from untrusted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall commercial_tiger_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 avoid using the 'commercial_tiger_0xrequest' package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'commercial_tiger_0xrequest' package has been identified as containing malicious code that can compromise the integrity of your npm projects. It is crucial to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for commercial_tiger_0xrequest →
FAQ
The malicious code can lead to the unauthorized modification of your project's package.json file, potentially exposing your application to further vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
Immediately uninstall the package and review your project for any dependencies that may have been affected. Consider replacing it with a safer alternative.
While specific alternatives depend on your project's requirements, consider searching the npm registry for similar packages that do not have a history of malicious activity.
