Malicious Code Injection in Thorough Crocodile Z3N Package

thorough_crocodile_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96996: Malicious code in thorough_crocodile_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

Thorough Crocodile Z3N is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the tea protocol ecosystem. However, it has been identified as being compromised, containing malicious scripts that can manipulate its own package metadata and publish harmful variants to the npm registry.

Vulnerability Detail

The vulnerability originates from the package's involvement in a scheme to inflate developer reputation scores for token rewards. It includes autopublish scripts that modify the package.json file, removing private flags and changing version numbers. This allows the package to generate and publish numerous derivative packages with randomized names, effectively polluting the npm registry and potentially leading to security risks for users who unknowingly install these malicious variants.

How To Fix

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

npm uninstall thorough_crocodile_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 Thorough Crocodile Z3N package until a secure version is released. Additionally, you can monitor your project for any unauthorized changes to package.json and regularly audit your dependencies.

Conclusion

The Thorough Crocodile Z3N package has been identified as containing malicious code that can compromise projects using it. It is essential to take immediate action by updating or removing the package to safeguard your application from potential threats.

See every vulnerability recorded for thorough_crocodile_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to facilitate certain functionalities within that ecosystem.

The vulnerability can lead to the installation of malicious variants that may compromise your project's integrity and security.

You should immediately update the package to a patched version or remove it from your project to prevent potential security risks.

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

Regularly auditing your dependencies, using tools like Vulert, and keeping your packages updated can help prevent similar vulnerabilities.

How To Fix

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

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