Malicious Code Injection in supreme_lemur_z3n: A Threat to npm Packages

supreme_lemur_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96884: Malicious code in supreme_lemur_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 supreme_lemur_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in supreme_lemur_z3n stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically publish variants with altered package.json files, removing private flags and changing version numbers. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for legitimate packages to be found. The malicious payload can lead to the unintentional installation of compromised packages, exposing applications to further security risks.

How To Fix

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

npm uninstall supreme_lemur_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, consider using a package-lock.json file to lock your dependencies to specific versions. This can help prevent the installation of compromised packages. You can also monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

Conclusion

The supreme_lemur_z3n package poses a significant security risk due to its association with a malicious campaign that exploits npm's publishing mechanisms. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your applications from potential threats.

See every vulnerability recorded for supreme_lemur_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.

You should uninstall the package immediately using the command npm uninstall supreme_lemur_z3n and review your dependencies for any other potential vulnerabilities.

You can use tools like Vulert, which allows you to monitor your package-lock.json file for open-source vulnerabilities without requiring any installation.

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

How To Fix

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

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