Malicious Code Vulnerability in corresponding_orca_0xrequest Package
Summary
MAL-2025-101023: Malicious code in corresponding_orca_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The corresponding_orca_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious code that modifies package metadata.
Vulnerability Detail
The vulnerability originates from the malicious code embedded in the corresponding_orca_0xrequest package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, potentially affecting other developers and projects that rely on npm packages. The malicious payload poses a significant risk as it can compromise the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall corresponding_orca_0xrequestIf 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 corresponding_orca_0xrequest package in your project. If it is already included, consider removing it from your package.json and running npm install to clean up your dependencies.
Conclusion
The corresponding_orca_0xrequest package contains a significant vulnerability due to malicious code that alters package metadata and can pollute the npm registry. It is crucial to remove this package from your project and monitor for any updates or patches. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.
See every vulnerability recorded for corresponding_orca_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of packages.
The malicious code modifies your package.json file, potentially compromising your project's integrity and reputation in the npm ecosystem.
You should remove the corresponding_orca_0xrequest package from your project and monitor for any updates or patches.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
