Malicious Code Vulnerability in ksp-client-registry Package

ksp-client-registry Updated 11 Oct 2026

Summary

11/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17771: Malicious code in ksp-client-registry (npm). Affects ksp-client-registry versions 100.100.100 – 100.100.101. 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 ksp-client-registry package is an npm library designed for client-side registry management. It allows developers to interact with package registries in a streamlined manner. However, this package has been found to contain malicious code that compromises user data and system integrity, making it a significant security risk.

Vulnerability Detail

The vulnerability originates from the ksp-client-registry@100.100.100 version, which includes a prebuilt native addon that opens a raw TCP socket to a hardcoded IP address (64.181.165.115). Upon loading, it sends sensitive environment variables such as HOSTNAME, npm_package_name, and npm_config_registry in an HTTP request. This behavior indicates a dependency-confusion attack designed to exfiltrate data from the victim's environment. The package's high version number and generic name suggest it may be an attempt to masquerade as a legitimate package, further complicating detection.

How To Fix

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

npm uninstall ksp-client-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 workaround, you can remove the ksp-client-registry package from your project until a secure version is released. Use the following command to uninstall it: npm uninstall ksp-client-registry.

Conclusion

The ksp-client-registry package has a critical vulnerability that allows malicious code to exfiltrate sensitive data. It is essential to update the package to a secure version and monitor your application for vulnerabilities to protect against potential attacks.

See every vulnerability recorded for ksp-client-registry →

Share this vulnerability

FAQ

The ksp-client-registry package is an npm library used for managing client-side interactions with package registries.

The vulnerability can lead to unauthorized data exfiltration, compromising sensitive environment variables and potentially exposing your application to further attacks.

Check the package's repository for any updates or patches. If a patched version is available, update to that version immediately.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit https://vulert.com for more information.

Yes, 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 ksp-client-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