Malicious Code Injection in probable_squirrel_0xrequest: A Threat to npm Packages
Summary
MAL-2025-107301: Malicious code in probable_squirrel_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 probable_squirrel_0xrequest is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant concern for the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in probable_squirrel_0xrequest stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The origin of this issue is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting developers seeking rewards through the tea.xyz campaign.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall probable_squirrel_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 package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include probable_squirrel_0xrequest in its dependencies. You can also use Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The probable_squirrel_0xrequest package poses a significant risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for probable_squirrel_0xrequest →
FAQ
probable_squirrel_0xrequest is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the security of applications that rely on this package or its derivatives.
You should uninstall the package immediately using 'npm uninstall probable_squirrel_0xrequest' and check for any other affected packages in your project.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
