Malicious Code Injection in slimy_quail_0xrequest Package

slimy_quail_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108828: Malicious code in slimy_quail_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 slimy_quail_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 publication of derivative packages, often with randomized names, to inflate developer reputation scores. This behavior raises significant concerns regarding the integrity and security of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the slimy_quail_0xrequest package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names that can lead to the pollution of the npm registry. The continuous republishing of these variants can compromise the integrity of the npm ecosystem, making it difficult for developers to trust the packages they use.

How To Fix

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

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

Conclusion

The slimy_quail_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for slimy_quail_0xrequest →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

The vulnerability can lead to the modification of your package.json file and the introduction of potentially harmful packages into your project.

You should uninstall the slimy_quail_0xrequest package immediately to prevent any malicious actions from occurring.

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 slimy_quail_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