Malicious Code Injection in quickest_lemming_z3n Package

quickest_lemming_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89885: Malicious code in quickest_lemming_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The quickest_lemming_z3n package is part of the npm ecosystem, typically used for various JavaScript applications. It is designed to facilitate development by providing reusable code components. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in quickest_lemming_z3n arises from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent applications. The malicious payload is designed to exploit developers' trust in the npm ecosystem, making it crucial to address this issue promptly.

How To Fix

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

npm uninstall quickest_lemming_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 quickest_lemming_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The quickest_lemming_z3n package is associated with a serious vulnerability that can compromise the integrity of applications relying on it. Immediate action is required to remove the package and monitor for any potential impacts. Utilizing tools like Vulert can help maintain the security of your software projects.

See every vulnerability recorded for quickest_lemming_z3n →

Share this vulnerability

FAQ

The quickest_lemming_z3n package is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.

This vulnerability can compromise the integrity of your application by introducing malicious code that modifies package configurations and republish variants to the npm registry.

If you have installed the quickest_lemming_z3n package, you should uninstall it immediately and check for any dependencies that may be affected.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application using the Vulert playground without any signup.

To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

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