Malicious Code Vulnerability in thin_tiger_z3n Package

thin_tiger_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109609: Malicious code in thin_tiger_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 thin_tiger_z3n package is part of the npm ecosystem, often utilized for various JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages designed to inflate developer reputation scores. This package, like others in its category, is vulnerable to exploitation due to its inherent design flaws that allow for the insertion of harmful scripts.

Vulnerability Detail

The vulnerability in the thin_tiger_z3n package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses significant risks to developers who may unknowingly use these tainted packages.

How To Fix

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

npm uninstall thin_tiger_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 thin_tiger_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The thin_tiger_z3n package poses a significant risk due to its malicious code that alters project files and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities to maintain security.

See every vulnerability recorded for thin_tiger_z3n →

Share this vulnerability

FAQ

The thin_tiger_z3n package is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.

You should uninstall the package immediately using 'npm uninstall thin_tiger_z3n' and check for any other affected packages.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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