Malicious Code Vulnerability in organisational_tyrannosaurus_z3n Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-122417: Malicious code in organisational_tyrannosaurus_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The organisational_tyrannosaurus_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate automatic publishing of derivative packages, which can lead to reputation inflation for developers participating in the tea protocol. However, it has been compromised, allowing for the injection of malicious code.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the organisational_tyrannosaurus_z3n package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially damaging the integrity of the ecosystem. Developers using this package may unknowingly contribute to the spread of malicious code, leading to security risks in their applications.

How To Fix

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

npm uninstall organisational_tyrannosaurus_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 organisational_tyrannosaurus_z3n package from your project by executing: npm uninstall organisational_tyrannosaurus_z3n. This will help mitigate the risk until a secure version is released.

Conclusion

The organisational_tyrannosaurus_z3n package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential threats.

See every vulnerability recorded for organisational_tyrannosaurus_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed for automatic publishing of derivative packages.

The malicious code modifies your package.json file, potentially leading to the publication of harmful packages and compromising your application's security.

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 without any signup.

If no patched version is available, it is advisable to uninstall the package to prevent any security risks.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to the latest secure versions.

How To Fix

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

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.