Malicious Code Injection in academic_iguana_z3n Package

academic_iguana_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93089: Malicious code in academic_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 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 academic_iguana_z3n package is part of the npm ecosystem, typically used for various academic and research-related functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that employs malicious scripts to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to pollution of the npm registry. The ramifications include potential exposure of sensitive information, unauthorized access to systems, and degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall academic_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 temporary measure, avoid using the academic_iguana_z3n package and consider alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any unauthorized changes.

Conclusion

The academic_iguana_z3n package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial to remove this package from your projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for academic_iguana_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to unauthorized changes in your project's dependencies, potentially exposing sensitive information and compromising security.

You should uninstall the academic_iguana_z3n package immediately and monitor your project for any unauthorized changes.

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.

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

How To Fix

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

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