Malicious Code Injection in Respective Unicorn 0xRequest Package
Summary
MAL-2025-107966: Malicious code in respective_unicorn_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 'respective_unicorn_0xrequest' package is part of the npm ecosystem, often utilized for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially compromising the integrity of applications that depend on it.
Vulnerability Detail
The vulnerability originates from the package's malicious intent to modify the 'package.json' file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can inflate developer reputation scores fraudulently and lead to the proliferation of insecure packages in the ecosystem, posing significant risks to applications that rely on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall respective_unicorn_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 'respective_unicorn_0xrequest' package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'respective_unicorn_0xrequest' package poses a significant security risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for respective_unicorn_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign aimed at manipulating the npm registry and inflating developer reputation scores.
The vulnerability can lead to the introduction of insecure and malicious code into your application, compromising its security and integrity.
You should uninstall the package immediately and monitor your application for any signs of compromise.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can check if your application is affected by visiting the Vulert playground.
Regularly update your dependencies, use tools like Vulert to monitor vulnerabilities, and avoid using packages from untrusted sources.
