Malicious Code Injection in impressive_lemming_0xrequest Package

impressive_lemming_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104025: Malicious code in impressive_lemming_0xrequest (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 impressive_lemming_0xrequest package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which aims to inflate developer reputation scores by flooding the npm registry with malicious packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to continuous republishing of variants that pollute the npm registry. This can result in compromised projects, loss of control over package versions, and potential security risks for applications relying on this package.

How To Fix

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

npm uninstall impressive_lemming_0xrequest

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 temporarily avoid using the impressive_lemming_0xrequest package in your project. If you need similar functionality, consider using alternative packages that are verified and do not have known vulnerabilities. You can uninstall the package with the following command: npm uninstall impressive_lemming_0xrequest.

Conclusion

The impressive_lemming_0xrequest package poses a significant security risk due to its involvement in a malicious campaign. It is crucial to remove this package from your projects and monitor for any similar vulnerabilities to ensure the integrity and security of your applications.

See every vulnerability recorded for impressive_lemming_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.

You should uninstall the impressive_lemming_0xrequest package immediately to mitigate any risks associated with its malicious behavior.

Yes, consider using other npm packages that provide similar functionality but do not have known vulnerabilities.

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

How To Fix

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

npm uninstall impressive_lemming_0xrequest

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