Which versions of commandor-cli are malicious?

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

How do I remediate commandor-cli if I installed it?

commandor-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed commandor-cli — how do I know if it already compromised me?

If commandor-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is commandor-cli part of a known attack campaign?

Yes — commandor-cli is associated with the IN-MAL-2026-018241 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 commandor-cli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for commandor-cli (version 1.0.0).

Malicious package

commandor-clinpm

commandor-cli is a confirmed malicious npm package (MAL-2026-14172) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in commandor-cli (npm)

MAL-2026-14172

Immediate action

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

npm uninstall commandor-cli

What this malware does

The postinstall script in [email protected] (scripts/postinstall.js) XOR-decodes a hardcoded URL using key 'stf2026' that resolves to https://github.com/bebraz1/qPzM50V1AKG0rVlH/releases/download/null/main.exe, writes the fetched bytes to %TEMP%\main.exe, and spawns the binary detached. On WSL a companion XOR-encoded blob decodes to a powershell.exe command that pipes the same URL through to execute the binary on the Windows host, extending reach to non-Linux installers. Alongside the dropper, the script assembles a bare IPv4 address from a split array ['193','70','34','101'] and POSTs a JSON install beacon carrying the resolved platform label to http://193.70.34.101:20099/vote over plain HTTP. The download source is a personal GitHub repository unrelated to any documented publisher, the binary is opaque with no hash or signature verification, and both the payload URL and the PowerShell bridge command are stored as XOR-encoded byte arrays rather than plaintext.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

75d139bce34f1d3290c34bb6da1c421bb579afb93672b44909ed0725eb70be3c

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for commandor-cli (version 1.0.0).
If you installed it — respond
commandor-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If commandor-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. commandor-cli 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-018241

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks commandor-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database