Malicious Code Injection in lively_falcon_z3n Package - npm Vulnerability

lively_falcon_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95287: Malicious code in lively_falcon_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 lively_falcon_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities. It is designed to automatically generate and publish derivative packages with altered metadata, which can lead to reputation inflation for malicious actors.

Vulnerability Detail

The vulnerability stems from the package's malicious payload that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant issues, including the potential for developers to unknowingly install compromised packages, thereby exposing their applications to further vulnerabilities.

How To Fix

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

npm uninstall lively_falcon_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, avoid using the lively_falcon_z3n package until a secure version is released. You can also monitor your dependencies using tools like Vulert, which allows you to check for vulnerabilities in your package-lock.json without requiring any installation. To use Vulert, visit https://vulert.com/scanner and upload your package-lock.json file to see if your application is affected.

Conclusion

The lively_falcon_z3n package poses a significant risk due to its malicious behavior of altering package metadata and republishing compromised versions. It is essential for developers to remove this package and monitor their dependencies to maintain the security of their applications.

See every vulnerability recorded for lively_falcon_z3n →

Share this vulnerability

FAQ

lively_falcon_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

If you have the lively_falcon_z3n package installed, your application may be at risk of using compromised code, which can lead to security breaches.

You should uninstall the package immediately and check your package-lock.json for any references to it. Consider using Vulert to monitor your dependencies.

Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.

You can use Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

How To Fix

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

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