Malicious Code Injection in controversial_cat_z3n Package

controversial_cat_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93788: Malicious code in controversial_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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The controversial_cat_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the controversial_cat_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts are designed to continuously republish these variants, leading to pollution of the npm registry and potential exploitation by malicious actors. The ramifications include loss of control over the package, potential security breaches, and damage to the reputation of developers associated with the affected package.

How To Fix

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

npm uninstall controversial_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 measure, you can avoid using the controversial_cat_z3n package and any of its derivatives. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The controversial_cat_z3n package poses a significant security risk due to its embedded malicious code. It is crucial for developers to remove this package from their projects and monitor for any potential vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the integrity of your software.

See every vulnerability recorded for controversial_cat_z3n →

Share this vulnerability

FAQ

It is an npm package involved in the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json, removes private flags, and can lead to the continuous republishing of compromised packages.

You should uninstall the controversial_cat_z3n package immediately using 'npm uninstall controversial_cat_z3n'.

Yes, consider using other npm packages that provide similar functionality without the associated risks of malicious code.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

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