Malicious Code Detected in cluster-registry Package - Security Alert

cluster-registry Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17204: Malicious code in cluster-registry (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 cluster-registry package is an npm module designed to facilitate the management of cluster configurations in Node.js applications. It allows developers to register and manage clusters effectively, enhancing application performance and scalability. However, this package has been compromised, leading to the introduction of malicious code that poses significant security risks to users.

Vulnerability Detail

The vulnerability in the cluster-registry package stems from the inclusion of malicious code that can potentially compromise the integrity of applications utilizing this package. This issue was identified in all versions starting from 0, indicating that any application relying on this package is at risk. The ramifications of this vulnerability include unauthorized access to sensitive data, potential data breaches, and exploitation of the affected systems by malicious actors.

How To Fix

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

npm uninstall cluster-registry

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 measure, consider removing the cluster-registry package from your project until a secure version is available. You can do this by executing the command: npm uninstall cluster-registry. This will help mitigate the risk while you seek alternative solutions.

Conclusion

The discovery of malicious code in the cluster-registry package poses a serious threat to applications that utilize it. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications from potential exploitation.

See every vulnerability recorded for cluster-registry →

Share this vulnerability

FAQ

The cluster-registry package is an npm module that helps manage cluster configurations in Node.js applications.

The vulnerability involves the presence of malicious code that can compromise application security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

As a workaround, consider uninstalling the cluster-registry package until a secure version is released.

Detailed information about this vulnerability can be found in the official GitHub repository for the cluster-registry package.

How To Fix

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

npm uninstall cluster-registry

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