Malicious Code Injection in aggressive_jackal_z3n Package

aggressive_jackal_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98609: Malicious code in aggressive_jackal_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The aggressive_jackal_z3n package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, aiming to inflate developer reputation scores for token rewards. This package is particularly concerning due to its ability to modify critical files and republish itself under random names.

Vulnerability Detail

The vulnerability originates from the aggressive_jackal_z3n package, which contains malicious code designed to alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names and continuously republish itself, polluting the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and a compromised npm ecosystem.

How To Fix

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

npm uninstall aggressive_jackal_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 the aggressive_jackal_z3n package by using npm's package-lock.json to monitor dependencies. Additionally, consider using the following command to uninstall the package: npm uninstall aggressive_jackal_z3n.

Conclusion

The aggressive_jackal_z3n package poses a significant threat due to its malicious code that alters package files and repopulates the npm registry. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your projects.

See every vulnerability recorded for aggressive_jackal_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as malicious, designed to manipulate package information and republish itself.

It can lead to unauthorized modifications of your package files and potentially expose your project to further security risks.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

You should immediately remove the aggressive_jackal_z3n package and update your project to ensure it is secure.

Yes, Vulert provides a service that uses package-lock.json to monitor and alert for vulnerabilities in your software.

How To Fix

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

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