kisama-jsnpm
Advisory published Updated
kisama-js is a confirmed malicious npm package (MAL-2026-15645) that runs destructive / sabotage code (malicious versions 0.1.8, 0.1.9, 0.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in kisama-js (npm)
What this malware does
[email protected] ships an obfuscated index.js that runs an HTTP+WebSocket agent binding 0.0.0.0:8000 by default and exposing /api/exec (POST) for shell command execution plus /api/ws/terminal backed by node-pty/bun-pty for interactive PTY control. It additionally exposes a full-filesystem REST surface (list/cat/upload/download/delete/move/cp) and cron/onetime task scheduling, giving any party who reaches the port full remote control of the installer's host. The agent contacts api.trycloudflare.com to publish itself through Cloudflare quick-tunnels, converting a local listener into an internet-reachable endpoint without the operator opening a port. Host fingerprinting is performed via icanhazip.com, ifconfig.me/ip, and api6.ipify.org, with OS/hostname/version collected via systeminformation and reported through the agent's status interface. index.js is heavily obfuscated (obfuscator.io string-array with ~1630 entries, control-flow flattening, ~3829 decoder inlines) and wraps process.stdout.write / process.stderr.write to suppress specific on-host diagnostic messages. The package also references the anonymous pastebin shz.al and declares a self-referential dependency on kisama-js ^0.3.0, pulling a different release line's code into the install of 0.4.8.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Destructive / sabotageFind it
Search your lockfiles and build artifacts for kisama-js (8 malicious versions).
If you installed it — respond
kisama-js carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If kisama-js 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 kisama-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.