Malicious Code Injection in separate_jay_requirement Package
Summary
MAL-2025-96527: Malicious code in separate_jay_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
Background
The separate_jay_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The functionality of this package is compromised, as it contains scripts that automatically generate and publish derivative packages, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the separate_jay_requirement package stems from its inclusion in a malicious campaign that 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 variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious code can affect developers by misrepresenting their contributions and can also lead to security vulnerabilities in dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall separate_jay_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 workaround, you can manually remove the separate_jay_requirement package from your project by executing the following command: npm uninstall separate_jay_requirement. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The separate_jay_requirement package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and utilize monitoring tools to safeguard their applications against such vulnerabilities.
See every vulnerability recorded for separate_jay_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.
You should uninstall the separate_jay_requirement package immediately and monitor your application for any further vulnerabilities.
Yes, you can use Vulert's playground to check your application for vulnerabilities without requiring any signup.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to their latest secure versions.
