Malicious Code Vulnerability in Respective_jay_z3n Package
Summary
MAL-2025-107961: Malicious code in respective_jay_z3n (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_jay_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate automatic publishing of derivative packages, which can inflate developer reputation scores. This package is particularly vulnerable due to its inclusion of scripts that modify package metadata and republish variants, leading to potential abuse of the npm registry.
Vulnerability Detail
The vulnerability stems from malicious code embedded in the respective_jay_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby polluting the npm registry. The malicious payload is part of a broader scheme to exploit npm for token rewards, which can lead to reputational damage for developers and 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 respective_jay_z3nIf 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_jay_z3n package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can use npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The respective_jay_z3n package contains malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.
See every vulnerability recorded for respective_jay_z3n →
FAQ
The respective_jay_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.
The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your project's integrity and reputation.
You should remove the respective_jay_z3n package from your project immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
