Malicious Code Injection in entitled_rat_0xrequest Package

entitled_rat_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102134: Malicious code in entitled_rat_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 entitled_rat_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised, making it a vector for malicious code that can affect developers and their projects.

Vulnerability Detail

The vulnerability in the entitled_rat_0xrequest package stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these tainted packages, leading to potential security breaches and loss of reputation.

How To Fix

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

npm uninstall entitled_rat_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 remove the entitled_rat_0xrequest package from your project by executing the command: 'npm uninstall entitled_rat_0xrequest'. This will prevent the execution of any malicious code associated with this package until a secure version is available.

Conclusion

The entitled_rat_0xrequest package poses a significant risk due to its malicious code that alters project files and affects the npm ecosystem. It is crucial for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of open-source projects.

See every vulnerability recorded for entitled_rat_0xrequest →

Share this vulnerability

FAQ

The entitled_rat_0xrequest package is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores.

This vulnerability can compromise your project's integrity by introducing malicious code that alters your package.json file and pollutes the npm registry.

You should immediately uninstall the entitled_rat_0xrequest package and check for any unauthorized changes in your project files.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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