Malicious Code Injection in excellent_constrictor_0xrequest: A Threat to npm Packages

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102309: Malicious code in excellent_constrictor_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 package excellent_constrictor_0xrequest 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 known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores through automated scripts that publish derivative packages with random names.

Vulnerability Detail

The vulnerability in excellent_constrictor_0xrequest originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include compromised developer reputations and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall excellent_constrictor_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 excellent_constrictor_0xrequest package from your project by executing: npm uninstall excellent_constrictor_0xrequest. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The excellent_constrictor_0xrequest package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for excellent_constrictor_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the package immediately and monitor for any updates or patches that may address the vulnerability.

Yes, Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities, ensuring your application remains secure.

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

How To Fix

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

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