Which versions of cmd2func are malicious?

The following PyPI versions of cmd2func are flagged malicious: 0.2.2, 0.2.3. Treat any of these as compromised.

How do I remediate cmd2func if I installed it?

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

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

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

Malicious package

cmd2funcPyPI

Malicious code in cmd2func (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5290

Immediate action

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

pip uninstall cmd2func

What this malware does

The package installs cmd2func-setup.pth, a.pth file that Python auto-loads at every interpreter start. The single-line payload uses the.pth import-trick with or exec(...) and mangled single-letter identifiers to smuggle a multi-statement body past review. When executed, the payload checks for a sentinel at /tmp/.bun_ran and, if absent, downloads the Bun runtime zip from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/bun-{platform}-{arch}.zip into /tmp/b/, extracts the bun binary, chmods it executable (0o775), and runs bun run _index.js against a JS file resolved via glob inside the package. The advertised purpose of cmd2func is Convert command to callable Python object — there is no legitimate need for an alternate JavaScript runtime. The combination of a hidden.pth auto-loader, obfuscated payload, alternate-runtime dropper, and unrelated JS execution is a covert dropper that fires on every Python interpreter invocation after install, not just at install time. The RECORD/metadata references the prior 0.2.1 version, consistent with a hijack of a previously legitimate package.

Versions 0.2.2, 0.2.3 were compromised.

Compromised packages start an obfuscated infostealer. The infostealer is a heavily obfuscated JavaScript code executed using Bun runtime on Python startup. It collectes all kinds of sensitive data, including API keys, credentials to package repositories, cryptocurrency assets, password manager data. Infostealer actively queries online services to collect additional secrets as well as attempts to gain persistence and spread further by publishing infected packages using collected credentials. Data are exfiltrated likely using Github. The code seems to threaten to wipe the user's data if it detects invalid GitHub tokens. Cleanup should be done with caution.

It seems to be related to the recent Mini Shai Hulud campaign.

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

Campaign: 2026-06-compr-woodpecker

Reasons (based on the campaign):

compromised-package
exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-credentials
abuses-pth
obfuscation
infostealer
The package contains code to detect if it is running in a sandbox environment.
exfiltration-crypto
files-exfiltration
destructive-actions

Malicious versions

2 flagged

0.2.20.2.3

Indicators of compromise (SHA-256)

c56f23d1c59dd91728afaa8ae022f711a719574aeeabc0e2eee8f5d93dd30d21

9308ab37378e86a6adad9ca85fa7888e9a9f370eea133415adc68ea3810621ea

3770293dd6cce24bf97433a78e083aee8710157617361ee9428d6b48ef87bf21

01a15f51e5e63c1de7516f5734211a4a077721fa79f1d8c2137873bc1fd98d23

055d480cc069717b82f618e12d453e7d8dc7d2e83bf77ae25ae23f71e73a1d1a

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

Campaign

2026-06-compr-woodpeckerIN-MAL-2026-006200

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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