Malicious Code Injection in light_bobcat_z3n Package - npm Vulnerability

light_bobcat_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-87784: Malicious code in light_bobcat_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The light_bobcat_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code modules. However, it has been identified as part of a malicious campaign that seeks to exploit the npm registry by publishing derivative packages with harmful scripts.

Vulnerability Detail

The vulnerability originates from the light_bobcat_z3n package being associated with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that include scripts designed to modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, ultimately leading to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may introduce vulnerabilities into their applications.

How To Fix

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

npm uninstall light_bobcat_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 light_bobcat_z3n package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The light_bobcat_z3n package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. It is crucial to stay informed about such vulnerabilities and take proactive measures to secure your projects.

See every vulnerability recorded for light_bobcat_z3n →

Share this vulnerability

FAQ

The light_bobcat_z3n package is a JavaScript package available on npm, intended for use in application development.

If your application uses the light_bobcat_z3n package, it may be at risk of introducing malicious code that can compromise security and functionality.

You should immediately update the package to the latest version or remove it from your project to mitigate any risks.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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