Malicious Code Injection in unique_perch_0xrequest Package

unique_perch_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110135: Malicious code in unique_perch_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The unique_perch_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign that aimed to inflate developer reputation scores through the creation and publication of derivative packages. The package's functionality is compromised due to the presence of malicious scripts that manipulate its metadata and behavior.

Vulnerability Detail

The vulnerability stems from the presence of malicious code in the unique_perch_0xrequest package, which is linked to the tea.xyz token reward campaign. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious payload can have serious ramifications, including the potential for developers to unknowingly use compromised packages, leading to security risks in their applications.

How To Fix

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

npm uninstall unique_perch_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 avoid using the unique_perch_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The unique_perch_0xrequest package contains malicious code that compromises its integrity and poses security risks to developers. It is crucial to remove this package from your projects and monitor for any similar vulnerabilities in the future. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for unique_perch_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

You should uninstall the unique_perch_0xrequest package immediately and check for any other dependencies that may have been affected.

While specific exploits have not been detailed, the manipulation of package metadata poses a significant risk for developers using the affected package.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

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