Malicious Code Injection in inquisitive_antelope_z3n: A Threat to npm Packages

inquisitive_antelope_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104239: Malicious code in inquisitive_antelope_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 inquisitive_antelope_z3n is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior aims to inflate developer reputation scores for rewards in the tea protocol, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in inquisitive_antelope_z3n stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the integrity of the packages, potentially affecting any projects that depend on them. The malicious payload is part of a broader strategy to exploit npm's ecosystem for token rewards, posing risks to developers and users alike.

How To Fix

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

npm uninstall inquisitive_antelope_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 inquisitive_antelope_z3n package in your project. Additionally, consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The inquisitive_antelope_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for inquisitive_antelope_z3n →

Share this vulnerability

FAQ

inquisitive_antelope_z3n is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project's dependencies and potentially introducing malicious code.

You should remove the inquisitive_antelope_z3n package from your project and monitor for any updates or patches that may be released.

Yes, Vulert can monitor your package-lock.json file for vulnerabilities in real-time, alerting you to any issues, including those related to inquisitive_antelope_z3n.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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