Which versions of ksp-client-registry are malicious?

The following npm versions of ksp-client-registry are flagged malicious: 100.100.100, 100.100.101. Treat any of these as compromised.

How do I remediate ksp-client-registry if I installed it?

ksp-client-registry is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed ksp-client-registry — how do I know if it already compromised me?

If ksp-client-registry was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is ksp-client-registry part of a known attack campaign?

Yes — ksp-client-registry is associated with the IN-MAL-2026-021422, IN-MAL-2026-021421 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ksp-client-registry across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ksp-client-registry (2 malicious versions).

Malicious package

ksp-client-registrynpm

Advisory published Oct 11, 2026Updated Oct 11, 2026

ksp-client-registry is a confirmed malicious npm package (MAL-2026-17771) that steals credentials and exfiltrates sensitive data (malicious versions 100.100.100, 100.100.101). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ksp-client-registry (npm)

MAL-2026-17771

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ksp-client-registry

What this malware does

The npm package [email protected] ships a prebuilt native addon at prebuilds/linux-x64/addon.node that is loaded by the package main (index.js require of./prebuilds/linux-x64/addon). On load the addon reads the HOSTNAME, npm_package_name, and npm_config_registry environment variables and opens a raw TCP socket to the hardcoded IP 64.181.165.115, sending them in an HTTP request of the form 'POST /dc HTTP/1.0' with a body shaped as 'h=<hostname>&p=<package>&u=<user>&r=<registry>'. ELF strings corroborate the behavior: '64.181.165.115', 'POST /dc HTTP/1.0', 'Host: 64.181.165.115', 'HOSTNAME', 'npm_package_name', 'npm_config_registry', and imports of socket/connect/send/fork/getenv/inet_pton. package.json declares a postinstall ('node postinstall.js') providing an install-time footprint, and any require() of the package triggers the beacon regardless. The addon exposes no legitimate N-API functionality beyond module registration. The implausibly high version (100.100.100) and generic registry-style name are consistent with a dependency-confusion probe designed to be resolved in place of an internal package and to report back the victim host, internal package name, and configured registry URL to the operator.

Malicious versions

2 flagged

100.100.100100.100.101

Indicators of compromise (SHA-256)

3b11a639f5149e4b1c17e64eb78f226abece5ed03152b5933333a3cb56284018

44dd37ed96611f26302ed323de01f14fba9077aa6798410193047ab11d7ffc81

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for ksp-client-registry (2 malicious versions).
If you installed it — respond
ksp-client-registry is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ksp-client-registry was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ksp-client-registry on npm has been identified as a malicious package (versions 100.100.100, 100.100.101 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021422IN-MAL-2026-021421

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ksp-client-registry-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database