Malicious Code Injection in strange_squirrel_requirement Package
Summary
MAL-2025-96800: Malicious code in strange_squirrel_requirement (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 strange_squirrel_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts that automatically generate and publish derivative packages with randomized names, modifying the package.json file to remove private flags and change version numbers. This behavior can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising the security of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall strange_squirrel_requirementIf 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 strange_squirrel_requirement package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The strange_squirrel_requirement package has been identified as a malicious entity within the npm ecosystem, posing significant risks to applications that utilize it. Developers are advised to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their projects.
See every vulnerability recorded for strange_squirrel_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
If your application uses this package, it may be at risk of having its dependencies polluted with malicious code, leading to potential security issues.
You should remove the strange_squirrel_requirement package from your project immediately and look for alternatives.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
