Malicious Code Vulnerability in outstanding_unicorn_requirement Package
Summary
MAL-2025-95816: Malicious code in outstanding_unicorn_requirement (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The outstanding_unicorn_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.
Vulnerability Detail
The vulnerability originates from a malicious campaign associated with the tea.xyz token reward initiative. The outstanding_unicorn_requirement package contains scripts designed to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which pollutes the npm registry. This behavior can compromise the integrity of the npm ecosystem and potentially lead to security risks for developers who unknowingly use these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall outstanding_unicorn_requirementIf 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 outstanding_unicorn_requirement package altogether. If it is already in use, consider removing it from your package.json and running npm install to clean up your dependencies.
Conclusion
The outstanding_unicorn_requirement package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and remain vigilant about the integrity of their dependencies. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for outstanding_unicorn_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should remove the outstanding_unicorn_requirement package from your project immediately and monitor for any updates or patches.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay updated on best practices for package management.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
