Malicious Code Injection in orthodox_lemming_0xrequest Package

orthodox_lemming_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106809: Malicious code in orthodox_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The orthodox_lemming_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. This package, like others in its category, has been identified as containing malicious scripts that compromise its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the orthodox_lemming_0xrequest package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The primary goal is to automate the creation and publication of numerous derivative packages, thereby polluting the npm registry and potentially leading to security risks for developers and users. The malicious payload can compromise the integrity of applications using this package, making them susceptible to further attacks or misuse.

How To Fix

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

npm uninstall orthodox_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 remove the orthodox_lemming_0xrequest package from your project until a secure version is released. Use the following command to uninstall it: npm uninstall orthodox_lemming_0xrequest. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The orthodox_lemming_0xrequest package contains a significant vulnerability due to malicious code that alters its functionality and compromises application security. It is crucial for developers to update or remove this package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for orthodox_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 compromise your application's integrity, leading to potential security risks and misuse.

Check the npm registry for the latest version of the orthodox_lemming_0xrequest package to see if a patch has been released.

You should update the package to the latest version or remove it from your project until a secure version is available.

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

How To Fix

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

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