Malicious Code Vulnerability in stiff_ant_z3n Package

stiff_ant_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109129: Malicious code in stiff_ant_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 stiff_ant_z3n package is part of the npm ecosystem and has been identified as a malicious package linked to the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by creating and publishing derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The package's functionality is compromised due to its malicious intent, posing a significant risk to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability originates from the package's design to include autopublish scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious code can affect developers by inflating reputation scores fraudulently and may lead to the installation of untrusted packages.

How To Fix

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

npm uninstall stiff_ant_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 measure, avoid using the stiff_ant_z3n package and monitor your dependencies for any signs of malicious activity. You can also use tools like Vulert to check if your application is affected by this vulnerability. For example, you can visit the Vulert playground at https://vulert.com/scanner to analyze your package-lock.json file without needing to sign up.

Conclusion

The stiff_ant_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for any signs of vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for stiff_ant_z3n →

Share this vulnerability

FAQ

The stiff_ant_z3n package is an npm package identified as malicious, designed to manipulate the npm registry for fraudulent purposes.

This vulnerability can lead to the installation of untrusted packages, inflate developer reputation scores fraudulently, and compromise the integrity of your project's dependencies.

You should uninstall the stiff_ant_z3n package immediately using 'npm uninstall stiff_ant_z3n' and check your project for any other potentially malicious packages.

Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to analyze your package-lock.json file for vulnerabilities without needing to create an account.

How To Fix

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

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