Which versions of cometlogger are malicious?

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

How do I remediate cometlogger if I installed it?

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

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

Yes — cometlogger is associated with the RLMA-2024-11009, RLUA-2025-00449, 2024-11-cometlogger, RLUA-2026-00219 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 cometlogger 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 cometlogger (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cometlogger across your stack and pipelines.

Malicious package

cometloggerPyPI

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

MAL-2024-11562

Immediate action

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

pip uninstall cometlogger

What this malware does

Multi-purpose infostealer, including grabbing cookies, files, information from cryptowallets; injecting code into discord application. This package is a builder for the actual malware

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

Campaign: 2024-11-cometlogger

Reasons (based on the campaign):

infostealer
files-exfiltration
peristence-autorun
clipboard-stealing
exfiltration-generic
exfiltration-crypto
exfiltration-browser-data
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

3def40076d6d9157e2c591320bc4028c4a449271b75f6719eab3c47957603f86

abdbb464ce08802fc7aa95512fc31af0a0fceaf4ade6d9ac98b67790a5323cd6

8783c1b024641baf7c5fd01e1fc0a300451e5eca34247485ec704939ebc64d69

627a435be86fedd2eccd2f0af61fa8b19c8c12dd781fc1bdc064d836e1eff19a

1006c0d5b4094e7049bf308e95dc9cf5cddf0fa0cef7b8bd4f0c1a9b123a9faf

c5a6c82583317a94093d7ecb14331808b88ecf9d2e3c5b1f97b37314116e7987

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 cometlogger (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cometlogger across your stack and pipelines.
If you installed it — respond
cometlogger 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 cometlogger 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 cometlogger 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. cometlogger 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

RLMA-2024-11009RLUA-2025-004492024-11-cometloggerRLUA-2026-00219

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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