Malicious Code Injection in residential_primate_0xrequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107938: Malicious code in residential_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 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 residential_primate_0xrequest package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages designed to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the residential_primate_0xrequest package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which are then continuously republished to pollute the npm registry. This behavior can lead to significant security risks, including the potential for unauthorized access to sensitive data and the compromise of project integrity.

How To Fix

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

npm uninstall residential_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 workaround, you can prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Additionally, consider using the following command to audit your dependencies for vulnerabilities: npm audit.

Conclusion

The residential_primate_0xrequest package poses a significant security risk due to its malicious code that alters project dependencies. It is crucial to remove this package and monitor for any updates to safeguard your project from potential threats.

See every vulnerability recorded for residential_primate_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to unauthorized modifications of your project's dependencies, potentially compromising its security and integrity.

You should remove the residential_primate_0xrequest package from your project and monitor for any updates or patches.

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

Vulert is a tool that monitors and alerts for open-source vulnerabilities in software using just the package-lock.json file.

How To Fix

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

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