Malicious Code Injection in previous_planarian_z3n Package - npm Vulnerability

previous_planarian_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89511: Malicious code in previous_planarian_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The previous_planarian_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names.

Vulnerability Detail

This vulnerability originates from the malicious code embedded in the previous_planarian_z3n package. It modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of data integrity.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall previous_planarian_z3n

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 remove the previous_planarian_z3n package from your project by executing the following command: npm uninstall previous_planarian_z3n. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The previous_planarian_z3n package contains malicious code that poses significant risks to developers and their projects. It is essential to take immediate action by updating or removing the package to safeguard your application from potential threats. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for previous_planarian_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code.

The code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

If an update is not available, consider removing the package from your project and looking for a secure alternative.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall previous_planarian_z3n

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback