# MAL-2026-15815: Malicious code in cminhouse-api-gateway-nodejs (npm)


- **Type:** Malicious package
- **Package:** `cminhouse-api-gateway-nodejs` (npm)
- **Published:** 2 Sep 2026

## What is MAL-2026-15815?

MAL-2026-15815 is a malicious package in cminhouse-api-gateway-nodejs, published on 2 Sep 2026. 

### Official description

index.js is wired as the package's `postinstall` script and also runs on `require` via `main`. After skipping CI/test/Docker environments (guards on NODE_ENV=test, CI, JEST_WORKER_ID, VITEST, /.dockerenv) and applying a random 5-15 second delay, it walks the installer's home directory and reads SSH private keys (~/.ssh/*), AWS credentials (~/.aws), Azure access tokens (~/.azure), gcloud config (~/.config/gcloud), Kubernetes, Docker, Terraform, GitHub, Vercel, Netlify, Supabase, and Firebase configuration files,.npmrc/.yarnrc,.netrc,.pgpass, database rc files, PyPI/cargo/gem credentials, and a HuggingFace token. It also iterates process.env selecting any variable whose name matches TOKEN/KEY/SECRET/PASSWORD/etc. The collected payload is base64-encoded and POSTed to a hardcoded bare-IP VPS at http://2.26.82.63:8888/collect, and host reconnaissance (username, hostname, platform, arch, cwd, node version) is separately sent to api.telegram.org via a hardcoded bot token and chat id with a '🎯 NEW VICTIM' tag. Sandbox-evasion gating, randomized delay, victim-tagging language, and a bare-IP exfiltration endpoint are all consistent with a targeted supply-chain credential-theft payload.

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

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

## Sources

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

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