Which versions of order-package-saas are malicious?

The following npm versions of order-package-saas are flagged malicious: 999.0.0, 999.0.1. Treat any of these as compromised.

How do I remediate order-package-saas if I installed it?

order-package-saas is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed order-package-saas — how do I know if it already compromised me?

If order-package-saas was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is order-package-saas part of a known attack campaign?

Yes — order-package-saas is associated with the IN-MAL-2026-019328, IN-MAL-2026-019327 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find order-package-saas across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for order-package-saas (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging order-package-saas across your stack and pipelines.

Malicious package

order-package-saasnpm

order-package-saas is a confirmed malicious npm package (MAL-2026-15816) that steals credentials and exfiltrates sensitive data (malicious versions 999.0.0, 999.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in order-package-saas (npm)

MAL-2026-15816

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall order-package-saas

What this malware does

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.

Malicious versions

2 flagged

999.0.0999.0.1

Indicators of compromise (SHA-256)

bb09ffe18928cf319d13dc52111750c394330d53b38b4d8814b0d2372471308e

e9cdb23f67bf90ab841c14a66b87c064c30abd9ba93609aa61ce7fcce74aeb1b

208338bb85a27cd136d36a4cd4797ccc697b42e175c9b400324648782c08b2fb

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for order-package-saas (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging order-package-saas across your stack and pipelines.
If you installed it — respond
order-package-saas is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If order-package-saas was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks order-package-saas before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. order-package-saas on npm has been identified as a malicious package (versions 999.0.0, 999.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019328IN-MAL-2026-019327

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks order-package-saas-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database