Malicious Code Injection in unknown_trout_z3n Package - npm Vulnerability

unknown_trout_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97160: Malicious code in unknown_trout_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 unknown_trout_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package 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. The package's functionality is compromised, leading to potential security risks for applications that depend on it.

Vulnerability Detail

This vulnerability originates from the malicious intent behind the unknown_trout_z3n package, which includes scripts that modify the package.json file to remove private flags and alter version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. The ramifications include unauthorized access to sensitive data, potential exploitation of the affected applications, and a significant increase in the risk of dependency confusion attacks.

How To Fix

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

npm uninstall unknown_trout_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 unknown_trout_z3n package and replace it with a reputable alternative. Always verify the integrity of packages before including them in your project. For example, you can use the following command to check for outdated packages: 'npm outdated'.

Conclusion

The unknown_trout_z3n package poses a significant security risk due to its malicious code designed to manipulate package metadata and publish unauthorized variants. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for unknown_trout_z3n →

Share this vulnerability

FAQ

The unknown_trout_z3n package is an npm package linked to a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.

The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially exposing sensitive data and increasing the risk of exploitation.

If you have installed the unknown_trout_z3n package, you should uninstall it immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.

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

How To Fix

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

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