What does the matlab-cli malware do?

Importing the module starts a reverse shell Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-05-matlab-cli Reasons (based on the campaign): - impersonation - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine. - obfuscation

Which versions of matlab-cli are malicious?

The following PyPI versions of matlab-cli are flagged malicious: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 0.9.1, 0.9.2, 1.0. Treat any of these as compromised.

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

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

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

Yes — matlab-cli is associated with the 2025-05-matlab-cli 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 matlab-cli 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 matlab-cli (12 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging matlab-cli across your stack and pipelines.

Malicious package

matlab-cliPyPI

Malicious code in matlab-cli (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191785

Immediate action

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

pip uninstall matlab-cli

What this malware does

Importing the module starts a reverse shell

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-05-matlab-cli

Reasons (based on the campaign):

impersonation
The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
obfuscation

Malicious versions

12 flagged

0.10.20.30.40.50.60.70.80.90.9.10.9.21.0

Indicators of compromise (SHA-256)

1bbbf182e70efaa8e13a47edbbb8ad9338bb3fc3cfe54cf8a2c4ac83fde1f3d2

ff0a277d45885a5c1a26f027495e73b5e0aa8b49c7ee3eeafd06cc14e6e8f754

2d2fb11265725c77cdafafed262e5d951018744fe0bd7e93da27b08dc94e87da

aec89a6a20203e70e79b9a1ddae471719032ab48c3faa1bc2ba01249322e068f

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 matlab-cli (12 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging matlab-cli across your stack and pipelines.
If you installed it — respond
matlab-cli 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 matlab-cli 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 matlab-cli 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. matlab-cli on PyPI has been identified as a malicious package (versions 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, and 4 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-05-matlab-cli

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks matlab-cli-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