Which versions of commandorjs are malicious?

The following npm versions of commandorjs are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate commandorjs if I installed it?

Remove commandorjs 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 commandorjs — how do I know if it already compromised me?

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

Yes — commandorjs is associated with the IN-MAL-2026-018235 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 commandorjs 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 commandorjs (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commandorjs across your stack and pipelines.

Malicious package

commandorjsnpm

commandorjs is a confirmed malicious npm package (MAL-2026-14174) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in commandorjs (npm)

MAL-2026-14174

Immediate action

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

npm uninstall commandorjs

What this malware does

[email protected] is a dropper disguised as an npm library. Its index.js exports an empty object; the only functional code is scripts/postinstall.js, which runs automatically on npm install. The postinstall script POSTs a JSON payload with platform/arch/node info to a hardcoded plain-HTTP endpoint at 193.70.34.101:20099/vote (host assembled from a split integer array). It then XOR-decodes obfuscated blobs (ADDON_ENC, BRIDGE_LAUNCHER_ENC, BRIDGE_SCRIPT_PRE_ENC, BRIDGE_SCRIPT_POST_ENC) using the 7-byte key 'stf2026' to reconstruct a github.com download URL and shell launcher commands. On Windows it downloads the decoded binary to %TEMP%/main.exe and launches it detached; on WSL/virtualized Linux it executes a decoded PowerShell-style bridge command to run the Windows payload on the host. URL and shell-command obfuscation, bare-IP plain-HTTP telemetry, write-to-temp with detached exec, and a WSL-to-Windows-host bridge together form an install-time remote-code-execution dropper.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bdd905d058d1f6d1d32c380316559a38d52610dc95295528c85ccf990df9b51b

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 commandorjs (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commandorjs across your stack and pipelines.
If you installed it — respond
Remove commandorjs 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 commandorjs 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 commandorjs 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. commandorjs on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018235

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks commandorjs-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

Explore

All malware advisories How O3 detects malware Vulnerability database