Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

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)

MAL-2026-15645
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall kisama-js

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

8 flagged
0.1.80.1.90.2.00.2.40.3.00.3.50.4.60.4.8

Indicators of compromise (SHA-256)

ae0be63d987cf5c8b04b9dfe20a03be79a53671d43635fe8a9bde6139cea0a11
3e89b89fe03f60e697ae9414d879e6a9efc13b6d8c3fdf474e30d87b89abf602
0179b9fe97920f04431eb6d6e94b46c6ef2889af5e55d6a0b79793097187fed3
57f1e4e185ca81c3a760960e14d52487e3bfa65aebfb825312aad99451ffc668
9c9ea9a393bb757f3c18ae54227c426cec3bdf1b0d5ca41d254975ddaf083358
a2ee11a1aee252ad79ad260c50bf63b5d38f188293526e69c76864102307d88a
08f910158e0ee0f3e7f1adfad6ae7dc58539b5b93d874d3db0f8268f3a5d9682
38db71c51075297ff2deeeeed0c638a51ea01cfb0bf9f79f609f7142a332b9c6
3da121d81e076389fdbdd4e94fc8ce924e86d39ee2da30e039fb2f024bc4e578

Detection & response playbook

Destructive / sabotage
  1. Find it

    Search your lockfiles and build artifacts for kisama-js (8 malicious versions).

  2. 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.

  3. 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

No. kisama-js on npm has been identified as a malicious package (versions 0.1.8, 0.1.9, 0.2.0, 0.2.4, 0.3.0, 0.3.5, 0.4.6, 0.4.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vqwx-8v7g-55j3IN-MAL-2026-019388IN-MAL-2026-019385IN-MAL-2026-019626IN-MAL-2026-019623IN-MAL-2026-019622IN-MAL-2026-019620IN-MAL-2026-019624IN-MAL-2026-019621

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.

Explore

kisama-js (npm) malicious package — MAL-2026-15645 | O3 Security