Malicious Code Injection in mutual_squirrel_0xrequest Package

mutual_squirrel_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106063: Malicious code in mutual_squirrel_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 mutual_squirrel_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publishing of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior makes the package particularly vulnerable to exploitation, as it can lead to the pollution of the npm registry and the potential for malicious code distribution.

Vulnerability Detail

The vulnerability in the mutual_squirrel_0xrequest package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, thereby flooding the npm registry with potentially harmful packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with various malicious npm packages aimed at manipulating developer reputation scores.

How To Fix

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

npm uninstall mutual_squirrel_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 mutual_squirrel_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The mutual_squirrel_0xrequest package contains a significant vulnerability that can lead to the injection of malicious code into projects. It is essential to remove this package and monitor your project for vulnerabilities using tools like Vulert. By staying informed and proactive, you can protect your applications from potential threats.

See every vulnerability recorded for mutual_squirrel_0xrequest →

Share this vulnerability

FAQ

It is an npm package that is part of a campaign to inflate developer reputation scores through automated package publishing.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the mutual_squirrel_0xrequest package immediately and check for any other affected packages in your project.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

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