Malicious Code Injection in tame_gopher_z3n Package

tame_gopher_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90906: Malicious code in tame_gopher_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 tame_gopher_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 generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by the presence of malicious code that modifies critical files.

Vulnerability Detail

The vulnerability in the tame_gopher_z3n package stems from malicious code that alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior is designed to pollute the npm registry and can lead to significant security risks, including unauthorized access to sensitive data and the potential for further exploitation of affected systems. The origin of this vulnerability is linked to a campaign aimed at manipulating npm's package publishing system.

How To Fix

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

npm uninstall tame_gopher_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 tame_gopher_z3n package from your project by executing: npm uninstall tame_gopher_z3n. This will prevent the malicious code from executing while you seek a secure alternative.

Conclusion

The tame_gopher_z3n package contains a significant vulnerability due to malicious code that alters essential files and can lead to severe security risks. It is crucial to update or remove this package to protect your application from potential exploitation.

See every vulnerability recorded for tame_gopher_z3n →

Share this vulnerability

FAQ

The tame_gopher_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your application to security risks and affecting its integrity.

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

If you cannot update the package, it is recommended to uninstall it and look for a secure alternative that does not have known vulnerabilities.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review your package.json file for any unauthorized changes.

How To Fix

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

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