Malicious Code Injection in whispering_primate_0xrequest Package

whispering_primate_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110831: Malicious code in whispering_primate_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 whispering_primate_0xrequest package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign linked to the tea.xyz token reward system. This package is designed to manipulate npm registry behaviors, potentially affecting developers' reputations and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores through the automatic generation and publication of derivative packages. The continuous republishing of these variants leads to pollution of the npm registry, posing risks to developers and users relying on legitimate packages.

How To Fix

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

npm uninstall whispering_primate_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, you can avoid using the whispering_primate_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The whispering_primate_0xrequest package poses significant risks due to its malicious code that manipulates npm registry behaviors. It is crucial for developers to uninstall this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help ensure the security of your open-source dependencies.

See every vulnerability recorded for whispering_primate_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at manipulating npm registry behaviors.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and affecting your developer reputation.

You should uninstall the package immediately and check for any dependencies that may be affected. Use 'npm uninstall whispering_primate_0xrequest' to remove it.

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 check your application at Vulert Scanner.

Yes, you should look for alternative packages that offer similar functionality without the associated risks of malicious behavior.

How To Fix

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

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