Malicious Code Injection in varying_planarian_requirement Package
Summary
MAL-2025-97242: Malicious code in varying_planarian_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 varying_planarian_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the installation and management of various packages. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the varying_planarian_requirement package, which is linked to the tea.xyz token reward campaign. This code is designed to modify the package.json file by removing private flags, altering version numbers, and creating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, potentially affecting developers' reputation scores and the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall varying_planarian_requirement
If 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 the varying_planarian_requirement package by using npm's package-lock.json to lock your dependencies. This will help maintain the integrity of your application until a permanent fix is implemented.
Conclusion
The varying_planarian_requirement package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for varying_planarian_requirement →
FAQ
It is an npm package used for managing dependencies in JavaScript applications but has been identified as malicious.
The code modifies package metadata, potentially leading to reputation damage and pollution of the npm registry.
You should uninstall the package immediately and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without signing up.