Malicious Code Injection in critical_tick_0xrequest Package - npm Vulnerability
Summary
MAL-2025-101083: Malicious code in critical_tick_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 critical_tick_0xrequest package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate certain operations related to the tea protocol, but it has been compromised to include harmful scripts that can affect developers and their projects.
Vulnerability Detail
The vulnerability in the critical_tick_0xrequest package stems from malicious code that modifies the package.json file to remove private flags and alters version numbers. This code generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. The origin of this vulnerability is linked to a campaign aimed at inflating developer reputation scores for token rewards, posing significant risks to developers who may unknowingly use this package in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall critical_tick_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 critical_tick_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall critical_tick_0xrequest.
Conclusion
The critical_tick_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate risks associated with open-source dependencies.
See every vulnerability recorded for critical_tick_0xrequest →
FAQ
It is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and flooding the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you identify affected packages.
Using this package can lead to the exposure of sensitive information, manipulation of your project's dependencies, and potential damage to your project's reputation due to the pollution of the npm registry.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with the latest security advisories from the npm community.
Immediately remove the package and check for any unauthorized changes in your project files. Consider using Vulert to scan your project for other potential vulnerabilities.
