Malicious Code Injection in nearby_jay_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95611: Malicious code in nearby_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 package 'nearby_jay_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm registry and poses risks to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'nearby_jay_z3n' originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants leads to pollution of the npm registry, making it difficult for developers to trust the packages they use. The ramifications include potential security breaches, loss of reputation for developers, and a compromised npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nearby_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 'nearby_jay_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project's dependencies for vulnerabilities.
Conclusion
The 'nearby_jay_z3n' package poses significant risks due to its malicious code designed to manipulate the npm registry. It is crucial for developers to take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for nearby_jay_z3n →
FAQ
The main risk is the potential for malicious code to be executed, which can compromise your project's security and integrity.
You can use Vulert's playground to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately and check for any dependencies that may be affected. Consider updating to a secure alternative.
Regularly monitor your dependencies using tools like Vulert and stay updated on security advisories related to the packages you use.
If you face issues, check your project's dependencies and ensure that no other packages rely on nearby_jay_z3n. You may need to find alternatives or update your code accordingly.
