Which versions of kalipto-runtime are malicious?

The following npm versions of kalipto-runtime are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate kalipto-runtime if I installed it?

kalipto-runtime 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.

I already installed kalipto-runtime — how do I know if it already compromised me?

If kalipto-runtime 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.

Is kalipto-runtime part of a known attack campaign?

Yes — kalipto-runtime is associated with the GHSA-g6f3-9j93-879j, IN-MAL-2026-011235 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find kalipto-runtime across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kalipto-runtime (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kalipto-runtime across your stack and pipelines.

Malicious package

kalipto-runtimenpm

kalipto-runtime is a confirmed malicious npm package (MAL-2026-11087) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kalipto-runtime (npm)

MAL-2026-11087

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall kalipto-runtime

What this malware does

The package's main entry (src/server.js) is a self-executing Express server that binds to 0.0.0.0 on port 3000 and exposes POST /execute, which passes the request body's command field directly to child_process.exec with a 30-second timeout. The endpoint is gated by an API key read from process.env.RUNTIME_API_KEY, but the package's tarball includes a.env file containing RUNTIME_API_KEY=kalipto_runtime_secret_123 — a shared secret known to anyone who downloads the package from npm. Because main points at this server, both npm start and require('kalipto-runtime') cause the listener to come up. Any installer who runs this package exposes an internet-reachable arbitrary-command-execution service to every network their host is attached to, authenticated by a publicly known key. This is a backdoor: any attacker with the package contents (i.e., anyone) can run arbitrary shell commands on any host running the package.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4edc1c5c90212c63aac45d49d3f67b13e97d9e503312e05ac51f3e88bcbbfd18

a918c615e1b451efabe6e88b3ecb90108abea31ac6b963be88c0a667e7a31f3a

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kalipto-runtime (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kalipto-runtime across your stack and pipelines.
If you installed it — respond
kalipto-runtime 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 kalipto-runtime 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-runtime 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

No. kalipto-runtime on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g6f3-9j93-879jIN-MAL-2026-011235

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks kalipto-runtime-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database