Malicious Code Injection in effective_jackal_z3n: A Threat to npm Packages

effective_jackal_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101891: Malicious code in effective_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 package effective_jackal_z3n is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain scripts designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The package's functionality is compromised by malicious code that alters its metadata and behavior.

Vulnerability Detail

The vulnerability in effective_jackal_z3n stems from its malicious payload, which modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to significant security risks, including the potential for dependency confusion and the spread of malicious software. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall effective_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 this package by using npm's package-lock.json to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using Vulert, which analyzes your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Conclusion

The effective_jackal_z3n package poses a significant security risk due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial to remove this package from your project and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for effective_jackal_z3n →

Share this vulnerability

FAQ

effective_jackal_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry.

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

You should remove the effective_jackal_z3n package from your project and monitor for any updates or patches.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

How To Fix

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

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