Malicious Code Injection in steep_tahr_z3n: A Threat to npm Packages

steep_tahr_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90752: Malicious code in steep_tahr_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'steep_tahr_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to interact with the npm registry, but it has been identified as malicious due to its functionality that includes autopublishing scripts. These scripts are intended to inflate developer reputation scores by generating and publishing numerous derivative packages with randomized names, which can lead to pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'steep_tahr_z3n' originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the proliferation of unwanted packages in the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall steep_tahr_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 prevent the installation of this malicious package by using the following command to uninstall it: npm uninstall steep_tahr_z3n. Additionally, consider using npm audit to check for vulnerabilities in your project.

Conclusion

The 'steep_tahr_z3n' package poses a significant risk due to its malicious behavior of modifying package.json and republishing unwanted packages. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the security of their applications. Regular monitoring and auditing of dependencies can help mitigate these risks.

See every vulnerability recorded for steep_tahr_z3n →

Share this vulnerability

FAQ

'steep_tahr_z3n' is an npm package associated with a token reward campaign that has been identified as malicious due to its behavior of autopublishing derivative packages.

The vulnerability can lead to the installation of unwanted and potentially harmful packages, compromising the security and integrity of your application.

You should uninstall the package immediately and check for any other dependencies that may be affected by similar vulnerabilities.

You can use tools like npm audit to check for vulnerabilities in your project. Additionally, consider using Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json.

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 steep_tahr_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