Malicious Code Injection in plastic_cat_z3n Package: A Threat to npm Users

plastic_cat_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95909: Malicious code in plastic_cat_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 plastic_cat_z3n package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts, which can lead to significant security risks for users relying on this package.

Vulnerability Detail

The vulnerability in the plastic_cat_z3n package stems from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to the installation of compromised packages by unsuspecting developers.

How To Fix

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

npm uninstall plastic_cat_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 avoid using the plastic_cat_z3n package and replace it with a trusted alternative. Additionally, you can use the following command to audit your npm packages for vulnerabilities: 'npm audit'. This will help identify any other potentially compromised packages in your project.

Conclusion

The plastic_cat_z3n package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to ensure the security of their projects.

See every vulnerability recorded for plastic_cat_z3n →

Share this vulnerability

FAQ

The plastic_cat_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks or malicious code into your project.

If you have installed the plastic_cat_z3n package, you should uninstall it immediately using 'npm uninstall plastic_cat_z3n' and check for any other affected packages.

You can use tools like Vulert to monitor your project for open-source vulnerabilities in real-time. Vulert requires only your package-lock.json file to provide alerts.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall plastic_cat_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