Malicious Code Injection in suspicious_tiger_z3n Package

suspicious_tiger_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96905: Malicious code in suspicious_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The suspicious_tiger_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, its functionality is compromised due to the presence of malicious code that alters package metadata and publishes harmful variants.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the suspicious_tiger_z3n package. This payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. It continuously republishes these variants to pollute the npm registry, posing a significant risk to developers and users relying on npm for package management. The malicious behavior can lead to reputation damage for developers and potential security risks for applications using these compromised packages.

How To Fix

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

npm uninstall suspicious_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 suspicious_tiger_z3n package and any packages that depend on it. Monitor your package-lock.json file for any unexpected changes and remove any suspicious packages immediately.

Conclusion

The suspicious_tiger_z3n package poses a significant security risk due to its embedded malicious code. It is crucial for developers to remove this package from their projects and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can help in identifying and managing such risks effectively.

See every vulnerability recorded for suspicious_tiger_z3n →

Share this vulnerability

FAQ

The suspicious_tiger_z3n package is an npm package associated with a token reward campaign that has been compromised by malicious code.

The malicious code modifies package metadata and repackages it, which can lead to security vulnerabilities and reputation damage for developers.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

You should uninstall the suspicious_tiger_z3n package immediately and review your project for any other potentially compromised packages.

There is no patch available for the suspicious_tiger_z3n package as it is recommended to remove it entirely from your project.

How To Fix

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

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