Which versions of commander-stable are malicious?

The following npm versions of commander-stable are flagged malicious: 15.100.101. Treat any of these as compromised.

How do I remediate commander-stable if I installed it?

Remove commander-stable from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed commander-stable — how do I know if it already compromised me?

If commander-stable 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 commander-stable part of a known attack campaign?

Yes — commander-stable is associated with the GHSA-mmcm-p5h7-xjhw 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 commander-stable 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 commander-stable (version 15.100.101). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commander-stable across your stack and pipelines.

Malicious package

commander-stablenpm

Malicious code in commander-stable (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192687

Immediate action

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

npm uninstall commander-stable

What this malware does

The package commander-stable was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'commander-stable' @ 15.100.101 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

15.100.101

Indicators of compromise (SHA-256)

5ccb7d8128b93aac626500a0dc68514710622a75ffc9933611c0c3eff12d91e6

65fe1eb016adcd74c343cd1628168fca4112c383c79d2e8580aa81b80a3d162f

d960435ff1d49dae38d3390836ed2ea98d8952b423ab906c750127f7c6bc023d

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for commander-stable (version 15.100.101). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commander-stable across your stack and pipelines.
If you installed it — respond
Remove commander-stable from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If commander-stable 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 commander-stable 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. commander-stable on npm has been identified as a malicious package (version 15.100.101 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mmcm-p5h7-xjhw

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks commander-stable-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring