Malicious Code Injection in Eclipsehunter Package: npm Vulnerability Overview

eclipsehunter Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171128: Malicious code in eclipsehunter (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Eclipsehunter is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate certain functionalities within the npm ecosystem. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages, ultimately harming the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in the Eclipsehunter package originates from its association with the tea.xyz token reward campaign, which has been known to deploy malicious scripts. These scripts, such as auto.js and autopublish.js, are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the reputation of developers and their packages.

How To Fix

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

npm uninstall eclipsehunter

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, you can avoid using the Eclipsehunter package altogether and look for alternative packages that provide similar functionalities without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The Eclipsehunter package has been identified as a source of malicious code that can compromise the integrity of npm projects. It is essential to remove this package from your project and monitor for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your software.

See every vulnerability recorded for eclipsehunter →

Share this vulnerability

FAQ

Eclipsehunter is an npm package involved in the tea.xyz token reward campaign, which has been identified as malicious.

The vulnerability can lead to unauthorized modifications in your package.json file and pollute the npm registry, affecting your project's integrity and reputation.

You should uninstall the Eclipsehunter package immediately using the command 'npm uninstall eclipsehunter' and monitor your project for any further issues.

Yes, Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall eclipsehunter

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