Malicious Code Injection in polite_iguana_z3n: A Threat to npm Ecosystem

polite_iguana_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95926: Malicious code in polite_iguana_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

polite_iguana_z3n is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in polite_iguana_z3n originates from its inclusion in a malicious campaign that floods the npm ecosystem with spam packages. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall polite_iguana_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 workaround, you can avoid using the polite_iguana_z3n package altogether. If it is already included in your project, consider removing it and replacing it with a trusted alternative. Additionally, you can use the following command to uninstall the package: npm uninstall polite_iguana_z3n.

Conclusion

The polite_iguana_z3n package poses a significant risk due to its malicious code that affects the npm ecosystem. It is crucial for developers to be aware of such vulnerabilities and take necessary actions to protect their projects. Regular monitoring and updates are essential to maintain security.

See every vulnerability recorded for polite_iguana_z3n →

Share this vulnerability

FAQ

polite_iguana_z3n is an npm package that is part of a token reward campaign, which has been identified as containing malicious code.

The vulnerability can lead to the installation of spam packages, which may compromise your project's integrity and security.

You should uninstall the package immediately and check for any other affected packages in your project.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

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