Skip to content
OpenAdvisories
Malicious MAL-2026-15645 GHSA-vqwx-8v7g-55j3

kisama-js

npm package · versions 0.4.6, 0.4.8, 0.3.5, 0.2.4, 0.2.0, 0.1.8, 0.3.0, 0.1.9

Reported Aug 31, 2026 · Updated Sep 4, 2026

If this package is installed

Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.

Details

Source: amazon-inspector (0179b9fe97920f04431eb6d6e94b46c6ef2889af5e55d6a0b79793097187fed3)
kisama-js@0.4.8 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.

Source: ghsa-malware (ae0be63d987cf5c8b04b9dfe20a03be79a53671d43635fe8a9bde6139cea0a11)
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.