Malicious Code Injection in lively_jackal_z3n Package

lively_jackal_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95289: Malicious code in lively_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The lively_jackal_z3n package is part of the npm ecosystem, often utilized for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to a polluted npm registry and potential security risks for developers using these packages.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the lively_jackal_z3n package, which is associated with the tea.xyz token reward campaign. This package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants can lead to a compromised npm registry, making it difficult for developers to trust the integrity of packages they rely on. The ramifications include potential exposure to further malicious code and a degraded developer experience due to the cluttered registry.

How To Fix

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

npm uninstall lively_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 avoid using the lively_jackal_z3n package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity of packages before installation.

Conclusion

The lively_jackal_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and adopt best practices for package management to safeguard their applications from potential threats.

See every vulnerability recorded for lively_jackal_z3n →

Share this vulnerability

FAQ

lively_jackal_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you have installed the lively_jackal_z3n package, you should uninstall it immediately using the command: npm uninstall lively_jackal_z3n.

Yes, you should look for trusted packages that provide similar functionalities and have a good reputation in the developer community.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from reputable sources.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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