Malicious Code Injection in steady_lemming_0xrequest Package

steady_lemming_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109107: Malicious code in steady_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 steady_lemming_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the steady_lemming_0xrequest package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores through the automatic generation and republishing of these packages, which can lead to pollution of the npm registry and potential security risks for applications that utilize these packages.

How To Fix

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

npm uninstall steady_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 temporary workaround, you can avoid using the steady_lemming_0xrequest package altogether. If it is a dependency of another package, consider looking for alternative packages that do not have this vulnerability.

Conclusion

The steady_lemming_0xrequest package has been identified as containing malicious code that poses a significant risk to applications using it. It is crucial to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your open-source software.

See every vulnerability recorded for steady_lemming_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can modify your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

You should uninstall the steady_lemming_0xrequest package immediately and check for any dependencies that may rely on it.

Currently, there are no patched versions available for the steady_lemming_0xrequest package.

How To Fix

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

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