# MAL-2026-15813: Malicious code in bt2-api-gateway-node-js (npm)


- **Type:** Malicious package
- **Package:** `bt2-api-gateway-node-js` (npm)
- **Published:** 1 Sep 2026

## What is MAL-2026-15813?

MAL-2026-15813 is a malicious package in bt2-api-gateway-node-js, published on 1 Sep 2026. 

### Official description

bt2-api-gateway-node-js@999.0.1 runs a postinstall-triggered IIFE in index.js that reads installer-owned secrets from disk — ~/.ssh private keys, ~/.aws/{credentials,config,sso/cache}, ~/.azure, gcloud ADC, ~/.kube/config, ~/.docker/config.json, gh hosts.yml, ~/.netrc, ~/.npmrc, ~/.pypirc, ~/.gem/credentials, ~/.cargo/credentials, ~/.pgpass, ~/.my.cnf, and vercel/netlify/supabase/firebase tokens — and sweeps process.env for TOKEN/KEY/SECRET/PASSWORD and AWS/AZURE/GITHUB/STRIPE variables. The collected data is JSON-serialized, base64-encoded, and POSTed to two hardcoded destinations: the Telegram Bot API (api.telegram.org/bot<token>/sendMessage) and http://2.26.82.63:8888/collect over plain HTTP. Execution aborts if NODE_ENV=test, CI=true, JEST_WORKER_ID or VITEST is set, or /.dockerenv exists, and is delayed by a randomized 5–15 second setTimeout to evade CI and sandbox observation. The version number (999.0.1) and package name are consistent with a dependency-confusion lure targeting an internal 'bt2-api-gateway' package.

The OpenSSF Package Analysis project identified 'bt2-api-gateway-node-js' @ 999.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

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

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-15813 is a malicious package: bt2-api-gateway-node-js (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-15813/ (Markdown: https://insights.sbomify.com/MAL-2026-15813/index.md)
```

## Sources

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

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