# MAL-2026-15816: Malicious code in order-package-saas (npm)


- **Type:** Malicious package
- **Package:** `order-package-saas` (npm)
- **Published:** 1 Sep 2026

## What is MAL-2026-15816?

MAL-2026-15816 is a malicious package in order-package-saas, published on 1 Sep 2026. 

### Official description

The package's postinstall hook executes index.js, which sweeps installer-owned secrets from the home directory (.npmrc,.yarnrc,.gitconfig,.git-credentials, ~/.ssh/* private keys, ~/.aws/credentials and SSO cache, GCP application_default_credentials, Azure tokens, kubeconfig, Docker config, Terraform credentials, GitHub CLI hosts, Heroku.netrc, Vercel/Netlify/Supabase/Firebase tokens, VSCode settings, PyPI/gem/cargo credentials) and enumerates process.env for values matching TOKEN/KEY/SECRET/PASSWORD patterns, including AI provider API keys. The collected data — together with hostname, username, platform, architecture, cwd and Node version — is base64-encoded and transmitted over HTTPS to api.telegram.org/bot<redacted>/sendMessage (chat_id 8607833954) and over HTTP to 2.26.82.63:8888/collect. Execution is gated to early-return when NODE_ENV=test, CI=true, JEST_WORKER_ID or VITEST are set, or /.dockerenv exists, and is delayed by a randomized 5–15 second sleep to evade sandbox and CI observation. The package name and 999.0.1 version are consistent with a dependency-confusion lure targeting an internal package.

The OpenSSF Package Analysis project identified 'order-package-saas' @ 999.0.1 (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-15816?

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-15816 is a malicious package: order-package-saas (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-15816/ (Markdown: https://insights.sbomify.com/MAL-2026-15816/index.md)
```

## Sources

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

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