Which versions of cobo-custdoy are malicious?

The following PyPI versions of cobo-custdoy are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate cobo-custdoy if I installed it?

cobo-custdoy is a typosquat — you almost certainly intended a legitimately-named package. Remove cobo-custdoy, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed cobo-custdoy — how do I know if it already compromised me?

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

Yes — cobo-custdoy is associated with the 2024-08-old-cobo-sectest 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 cobo-custdoy 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 cobo-custdoy (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cobo-custdoy across your stack and pipelines.

Malicious package

cobo-custdoyPyPI

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

MAL-2024-12237

Immediate action

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

pip uninstall cobo-custdoy

What this malware does

It appears to be a forgotten pentest checking typosquatting against cobo-custody package, but may also have malicious purposes. During installation, if a machine is Mac, an obfuscated code attempts to download and execute a shell script. Currently, the server does not respond.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-08-old-cobo-sectest

Reasons (based on the campaign):

Downloads and executes a remote executable.
clones-real-package
crypto-related
The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation
typosquatting

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

98dab70ba7fa041c334d8111fdca72c44082587ae31c06aea908b24a8c34d238

1bb6da528665b6d869e583cb594f1f0cc7e7ccaf8cc5a7a859c0db9e7fa80c19

6595e9aeeff235159a58718b78afd8b8616fa995d9b16f572a256930099fa19d

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cobo-custdoy (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cobo-custdoy across your stack and pipelines.
If you installed it — respond
cobo-custdoy is a typosquat — you almost certainly intended a legitimately-named package. Remove cobo-custdoy, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If cobo-custdoy 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 cobo-custdoy 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. cobo-custdoy on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-08-old-cobo-sectest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks cobo-custdoy-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