Which versions of clawdest are malicious?

The following PyPI versions of clawdest are flagged malicious: 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7. Treat any of these as compromised.

How do I remediate clawdest if I installed it?

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

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

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

Malicious package

clawdestPyPI

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

MAL-2026-897

Immediate action

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

pip uninstall clawdest

What this malware does

The package is prepared to download a hardcoded executable and save it in %LOCALAPPDATA% under a very generic name, clearly aiming to hide its existence. Code is also prepared to alter MarkOfTheWeb, start as admin and run the executable, but in analyzed versions this behavior was not triggered in any existing code path. The downloading will happen e.g. on starting the declared command line.

Remote executables are standalone applications or installators, including ClickOnce installators. However, in the analysis attempts, none of them showed clear malicious behavior, in most cases crashing during the analysis. Captured network traffic shows communication with the remote server and likely expects the URL of the next stage, which was not delivered from the server. Additionally, the code embeds a separate path for execution on non-Windows machines. It attempts to execute a remote script, but in analyzed versions, the domain used is already suspended and not reachable.

In newer packages the remote code is another downloader, which then downloads a PyInstaller-packed executable that just calls back home but has no more functionality.

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

Campaign: 2026-02-magichat

Reasons (based on the campaign):

Downloads and executes a remote executable.
other
typosquatting

Malicious versions

6 flagged

1.1.21.1.31.1.41.1.51.1.61.1.7

Indicators of compromise (SHA-256)

3b0726c697eade2e1e1a90ae57775a95b2ef154b400ce8550fdede68d70df601

03d2f8e0e88d0311b9fa4d83c042d59ab998e0371feedba425830401ca744153

cc426fd1f3212fb6f7618a4bf3eba4368d6ce501482c682fe7e7f36f5ddd000e

8c1000e0277889b29ab6e6299a0321d5f5bffa9dc35ee18c0e673e4bca2c0dad

cf31ecc1ce2cf9d018d5ea73c9ee8467f85efd2fda44d75dfd10797cb35778a2

00be534666fb3892670113904d3b112ad628f6e862cb5179e89cce651143e5e5

bd4f9f2a718883fd7a2462f0a9cf451731a162e27c370b4eaeb87142e888ba5c

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

Campaign

2026-02-magichat

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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