# MAL-2026-11087: Malicious code in kalipto-runtime (npm)


- **Type:** Malicious package
- **Package:** `kalipto-runtime` (npm)
- **Published:** 27 Jul 2026
- **Also known as:** GHSA-g6f3-9j93-879j

## What is MAL-2026-11087?

MAL-2026-11087 is a malicious package in kalipto-runtime, published on 27 Jul 2026. 

### Official description

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.

## What should I do about MAL-2026-11087?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11087 is a malicious package: kalipto-runtime (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-11087/ (Markdown: https://insights.sbomify.com/MAL-2026-11087/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11087

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11087/
Summaries are generated and may contain mistakes; the official description above is the record.