Malicious Code Injection in continuous_tiglon_0xrequest Package
Summary
MAL-2025-100949: Malicious code in continuous_tiglon_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 continuous_tiglon_0xrequest package is part of the npm ecosystem and has been associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards but has been compromised to include malicious scripts that manipulate package metadata. The vulnerability allows attackers to exploit the package for nefarious purposes, including the generation of derivative packages that can clutter the npm registry.
Vulnerability Detail
The vulnerability stems from malicious code embedded in the continuous_tiglon_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to the continuous republishing of these variants. This not only inflates developer reputation scores fraudulently but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The malicious payload is linked to a broader campaign aimed at exploiting npm for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall continuous_tiglon_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 continuous_tiglon_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The continuous_tiglon_0xrequest package has been identified as containing malicious code that poses a significant risk to developers and their projects. It is essential to uninstall this package and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your software by providing real-time alerts for vulnerabilities.
See every vulnerability recorded for continuous_tiglon_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious code.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can clutter the npm registry and inflate developer reputation scores fraudulently.
You should uninstall the continuous_tiglon_0xrequest package immediately using the command: npm uninstall continuous_tiglon_0xrequest.
Yes, you should look for other npm packages that provide similar functionality without the associated risks.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.
