Malicious Code Injection in quick_peacock_0xrequest Package

quick_peacock_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107648: Malicious code in quick_peacock_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

The quick_peacock_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate requests in a quick and efficient manner. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful packages, which can compromise the integrity of applications relying on it.

Vulnerability Detail

The vulnerability in the quick_peacock_0xrequest package originates from its association with the tea.xyz token reward campaign. This campaign utilizes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The result is a continuous republishing of these variants, which pollutes the npm registry and can lead to security risks for developers and users alike.

How To Fix

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

npm uninstall quick_peacock_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 quick_peacock_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The quick_peacock_0xrequest package poses a significant security risk due to its malicious code that alters package configurations. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for quick_peacock_0xrequest →

Share this vulnerability

FAQ

It is an npm package used for making quick requests in JavaScript applications, but it has been compromised with malicious code.

If your application uses the quick_peacock_0xrequest package, it may be at risk of having its package.json modified and could lead to security breaches.

You should uninstall the quick_peacock_0xrequest package immediately and look for alternative solutions.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review the security advisories for the packages you use.

How To Fix

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

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