Malicious Code Injection in Respective Squirrel 0xRequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107964: Malicious code in respective_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 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

Respective Squirrel 0xRequest is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate token rewards through various automated scripts. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the respective_squirrel_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use this package, as it can compromise their projects and inflate developer reputation scores fraudulently.

How To Fix

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

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

Conclusion

The respective_squirrel_0xrequest package poses significant security risks due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for respective_squirrel_0xrequest →

Share this vulnerability

FAQ

The package contains malicious code that alters package metadata and floods the npm registry with derivative packages.

You can use Vulert to monitor your application for vulnerabilities. Simply upload your package-lock.json file to Vulert's playground at Vulert Scanner.

You should uninstall the respective_squirrel_0xrequest package immediately to mitigate any potential risks.

Yes, consider looking for other npm packages that provide similar functionalities without the malicious implications.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software.

How To Fix

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

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