Malicious Code Injection in many_lark_0xrequest Package: A Threat to npm Users

many_lark_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105604: Malicious code in many_lark_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 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 many_lark_0xrequest package is part of a broader campaign targeting npm users, associated with the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. Its functionality is compromised by malicious scripts that manipulate package metadata, posing a significant risk to users relying on this package.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the many_lark_0xrequest package, which is linked to a campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also compromises the integrity of the software supply chain, potentially leading to further exploitation by attackers.

How To Fix

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

npm uninstall many_lark_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 measure, you can avoid using the many_lark_0xrequest package and replace it with a trusted alternative. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The many_lark_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Users are advised to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for many_lark_0xrequest →

Share this vulnerability

FAQ

The many_lark_0xrequest package is part of a malicious campaign that automates the creation of derivative npm packages to inflate developer reputation scores.

The vulnerability can lead to the injection of malicious code, compromising the integrity of your application and potentially exposing it to further attacks.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

If you have installed the many_lark_0xrequest package, it is recommended to remove it immediately and replace it with a secure alternative.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your dependencies effectively.

How To Fix

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

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