Malicious Code Injection in unhappy_cockroach_z3n Package

unhappy_cockroach_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91525: Malicious code in unhappy_cockroach_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The unhappy_cockroach_z3n package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts, making it susceptible to malicious exploitation.

Vulnerability Detail

The vulnerability in the unhappy_cockroach_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores by polluting the npm registry with derivative packages. The ramifications include potential security risks for applications using this package, as it can lead to unauthorized access or manipulation of the package's functionality.

How To Fix

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

npm uninstall unhappy_cockroach_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 unhappy_cockroach_z3n package from your project by executing: npm uninstall unhappy_cockroach_z3n. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The unhappy_cockroach_z3n package contains a significant vulnerability due to malicious code that alters critical package information. It is crucial to update or remove this package to protect your application from potential security threats. Utilizing tools like Vulert can help monitor your dependencies for vulnerabilities effectively.

See every vulnerability recorded for unhappy_cockroach_z3n →

Share this vulnerability

FAQ

The unhappy_cockroach_z3n package is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

The malicious code modifies your package.json file, potentially leading to unauthorized access and manipulation of your application.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

If you cannot update the package, consider uninstalling it temporarily to mitigate any risks associated with the vulnerability.

Regularly check your dependencies using tools like Vulert, which provides real-time alerts for open-source vulnerabilities.

How To Fix

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

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