Malicious Code Injection in improved_hare_z3n Package

improved_hare_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94964: Malicious code in improved_hare_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The improved_hare_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which employs scripts to automatically generate and publish derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications include potential exposure of sensitive data, increased risk of dependency confusion attacks, and overall degradation of the npm ecosystem.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall improved_hare_z3n

If 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, consider removing the improved_hare_z3n package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall improved_hare_z3n'. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The improved_hare_z3n package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to stay informed about such vulnerabilities and take immediate action to secure their projects by updating or removing affected packages.

See every vulnerability recorded for improved_hare_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to unauthorized changes in your package.json, potential exposure of sensitive data, and pollution of the npm registry.

Check the npm registry for the latest version of improved_hare_z3n to see if a patched version is available.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Remove the affected package and monitor your project for any unauthorized changes. Update to a secure version as soon as it is available.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall improved_hare_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback