@ks-openclaw/kimnpm
Advisory published Updated
@ks-openclaw/kim is a confirmed malicious npm package (MAL-2026-11528) that opens a backdoor for remote access (malicious versions 99.0.0, 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @ks-openclaw/kim (npm)
What this malware does
The package's preinstall lifecycle script (preinstall.js) opens a TCP socket to the hardcoded remote host 120.55.170.103:8888, spawns cmd.exe, and pipes the shell's stdio through the socket, giving the remote party full interactive command execution on the installer's machine during npm install. The same script also collects installer host identifiers (os.hostname(), os.userInfo().username, os.platform(), process.version, process.cwd()) while the reverse shell is connected. Cover-story strings in the file ("Proof of Concept", "Dependency Confusion") do not change the observed behavior: install-time remote code execution against the installer.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for @ks-openclaw/kim (2 malicious versions).
If you installed it — respond
@ks-openclaw/kim establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @ks-openclaw/kim 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @ks-openclaw/kim-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.