Malicious Code Injection in dominant_jaguar_0xrequest Package

dominant_jaguar_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101700: Malicious code in dominant_jaguar_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 dominant_jaguar_0xrequest package is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to manipulate npm registry entries by generating and publishing derivative packages with randomized names, ultimately inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of autopublish scripts that automate the creation of these malicious packages.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the dominant_jaguar_0xrequest package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers by misrepresenting their contributions and could lead to security risks if other packages depend on these compromised versions.

How To Fix

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

npm uninstall dominant_jaguar_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 dominant_jaguar_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks. Regularly monitor your package dependencies for any updates or vulnerabilities.

Conclusion

The dominant_jaguar_0xrequest package poses a significant risk due to its malicious behavior, which can compromise the integrity of the npm registry and affect developers' reputations. It is essential to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert.

See every vulnerability recorded for dominant_jaguar_0xrequest →

Share this vulnerability

FAQ

It is an npm package identified as malicious, associated with the tea.xyz token reward campaign, which manipulates npm registry entries.

The vulnerability can lead to the pollution of the npm registry, misrepresentation of developer contributions, and potential security risks for dependent packages.

You should uninstall the dominant_jaguar_0xrequest package immediately using the command npm uninstall dominant_jaguar_0xrequest.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by visiting the Vulert playground.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

How To Fix

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

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