Malicious Code Injection in distant_jay_z3n Package - npm Vulnerability
Summary
MAL-2025-101637: Malicious code in distant_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 distant_jay_z3n package is part of the npm ecosystem and has been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. This package is designed to manipulate npm's package registry by generating and publishing derivative packages with random names, which can inflate developer reputation scores. The malicious nature of this package poses significant risks to the integrity of the npm registry and the security of applications relying on it.
Vulnerability Detail
The vulnerability in the distant_jay_z3n package stems from its inclusion in a broader malicious campaign that utilizes autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes developers to potential security risks, as these malicious packages can be inadvertently installed in projects, leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall distant_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 distant_jay_z3n package and any other packages that may be part of the tea.xyz token reward campaign. Regularly audit your package dependencies and remove any suspicious or unverified packages from your project.
Conclusion
The distant_jay_z3n 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 from their projects and to regularly audit their dependencies for vulnerabilities. Utilizing tools like Vulert can help in monitoring and maintaining the security of your applications.
See every vulnerability recorded for distant_jay_z3n →
FAQ
The distant_jay_z3n package is an npm package identified as part of a malicious campaign aimed at manipulating the npm registry.
If your application uses the distant_jay_z3n package, it may be at risk of incorporating malicious code that can compromise its security and integrity.
You should uninstall the distant_jay_z3n package immediately using the command npm uninstall distant_jay_z3n and audit your other dependencies for similar vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
