Malicious Code Injection in depressed_lion_z3n: A Threat to npm Packages

depressed_lion_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93989: Malicious code in depressed_lion_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 package 'depressed_lion_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code among developers. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with altered metadata. This behavior not only affects the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in 'depressed_lion_z3n' originates from its association with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The malicious payload within this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby polluting the npm registry. This can lead to developers inadvertently using compromised packages, which may contain harmful code or lead to reputation inflation for malicious actors.

How To Fix

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

npm uninstall depressed_lion_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 workaround, you can monitor your project for any dependencies that may include 'depressed_lion_z3n' and remove them. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can access Vulert's playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.

Conclusion

The 'depressed_lion_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant about the packages they use and to regularly check for vulnerabilities. By removing this package and utilizing tools like Vulert, developers can help maintain the integrity of their projects and the broader npm community.

See every vulnerability recorded for depressed_lion_z3n →

Share this vulnerability

FAQ

'depressed_lion_z3n' is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

Using 'depressed_lion_z3n' can lead to the inclusion of malicious code in your project, potentially compromising your application's security.

You should uninstall 'depressed_lion_z3n' immediately using 'npm uninstall depressed_lion_z3n' and review your dependencies for any other malicious packages.

Regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your package-lock.json.

Yes, you can use Vulert's playground at Vulert Scanner to check your application for vulnerabilities without needing to create an account.

How To Fix

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

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