Malicious Code Injection in continuous_catshark_z3n Package

continuous_catshark_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93779: Malicious code in continuous_catshark_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 continuous_catshark_z3n package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in the campaign, is designed to automate the generation and publication of derivative packages, often leading to malicious activities.

Vulnerability Detail

The vulnerability in the continuous_catshark_z3n package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants of the package, polluting the npm registry and potentially compromising the integrity of applications that depend on it. The origin of this issue is linked to the tea.xyz token reward campaign, which employs such tactics to manipulate developer reputation.

How To Fix

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

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

Currently, the best workaround is to avoid using the continuous_catshark_z3n package altogether. If it is already in use, ensure to remove it and monitor your application for any dependencies that may have been affected by this malicious package.

Conclusion

The continuous_catshark_z3n package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial to remove this package from your projects and monitor for any dependencies that may have been impacted. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.

See every vulnerability recorded for continuous_catshark_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for generating and publishing malicious derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.

Currently, there is no patched version available for the continuous_catshark_z3n package.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can also check your application for this vulnerability using the Vulert playground at Vulert Scanner.

You should uninstall the continuous_catshark_z3n package immediately and check for any dependencies that may have been affected.

How To Fix

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

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