Malicious Code Injection in remote_hare_z3n Package - npm Vulnerability
Summary
MAL-2025-89930: Malicious code in remote_hare_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 remote_hare_z3n package 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 exploit the npm registry by publishing numerous derivative packages with altered metadata. The primary functionality of this package is to serve as a token reward mechanism, but it has been compromised to inflate developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability in the remote_hare_z3n package stems from its association with the tea.xyz token reward campaign, which has been linked to the distribution of malicious code. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious payload can potentially harm developers by misleading them about the integrity of their dependencies and can also affect the overall health of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall remote_hare_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 prevent the installation of the remote_hare_z3n package by using npm's package-lock.json file to lock your dependencies. This will help ensure that the malicious package is not inadvertently installed in your project. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The remote_hare_z3n package poses a significant risk due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial for developers to be vigilant and remove this package from their projects to maintain the integrity of their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.
See every vulnerability recorded for remote_hare_z3n →
FAQ
The remote_hare_z3n package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
This vulnerability can lead to the installation of malicious code that alters your project's dependencies and can mislead developers about the integrity of their packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have already installed the remote_hare_z3n package, you should uninstall it immediately using 'npm uninstall remote_hare_z3n' and check your package-lock.json for any references.
Currently, there is no patched version available for the remote_hare_z3n package. It is recommended to remove the package and monitor for any updates.
