@kalipto/localnpm
Malicious code in @kalipto/local (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
The package is a purpose-built remote-control agent. On startup (when the bin is invoked with --token, e.g. npx @kalipto/local --token...), index.js opens a plaintext WebSocket connection to ws://api.kaliptosal.dev:3001 and sends a register message containing the host's process.env.HOSTNAME, process.platform, and the supplied token (index.js:27-34). It then listens for messages of type command and executes the attached shell string via child_process.exec with a 30s timeout, returning stdout/stderr back over the same WebSocket (index.js:43-58). The operator of api.kaliptosal.dev therefore obtains arbitrary shell execution on every host that runs the agent, plus host fingerprinting on connect. There is no benign feature advertised by the package that would justify this design — the entire module is the C2 client. Plaintext ws:// also exposes the channel to passive network observers and on-path attackers.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @kalipto/local (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @kalipto/local across your stack and pipelines.
If you installed it — respond
@kalipto/local 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 @kalipto/local was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @kalipto/local before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @kalipto/local-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.