Malicious Code Injection in open_sole_requirement Package
Summary
MAL-2025-95753: Malicious code in open_sole_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 open_sole_requirement package is part of the npm ecosystem, typically used for managing dependencies in JavaScript applications. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages. This package is particularly vulnerable due to its association with scripts that automate the publishing of malicious variants.
Vulnerability Detail
The vulnerability originates from the package being part of a broader malicious campaign associated with the tea.xyz token reward initiative. The malicious payload within the package modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which can pollute the npm registry and compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall open_sole_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 open_sole_requirement package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify any vulnerabilities.
Conclusion
The open_sole_requirement package has been identified as a vector for malicious code injection, posing significant risks to applications that utilize it. Immediate action is required to remove the package and mitigate potential threats. Regular monitoring and auditing of dependencies are crucial for maintaining application security.
See every vulnerability recorded for open_sole_requirement →
FAQ
The open_sole_requirement package is an npm package used for managing dependencies in JavaScript applications, but it has been compromised by malicious actors.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
If you have installed the open_sole_requirement package, you should uninstall it immediately and check for any dependencies that may be affected.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
