Malicious Code Injection in mutual_limpet_0xrequest Package

mutual_limpet_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106059: Malicious code in mutual_limpet_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The mutual_limpet_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions with the tea protocol, but it has been compromised to include malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the mutual_limpet_0xrequest package, which is part of a broader scheme to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and creating random package names, leading to pollution of the npm registry. This can result in security risks for developers who inadvertently use these compromised packages, as they may introduce vulnerabilities into their applications.

How To Fix

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

npm uninstall mutual_limpet_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, avoid using the mutual_limpet_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The mutual_limpet_0xrequest package contains malicious code that can compromise your application by altering package metadata and polluting the npm registry. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities.

See every vulnerability recorded for mutual_limpet_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to facilitate interactions with the tea protocol.

The malicious code can alter your package metadata, potentially leading to the introduction of vulnerabilities and pollution of the npm registry.

You should uninstall the mutual_limpet_0xrequest package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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