Which versions of pyclogger are malicious?

The following PyPI versions of pyclogger are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate pyclogger if I installed it?

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

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

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

Malicious package

pycloggerPyPI

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

MAL-2026-1099

Immediate action

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

pip uninstall pyclogger

What this malware does

Package contains an infostealer exfiltrating Discord tokens and saved browser credentials to a hardcoded location.

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

Campaign: 2026-02-pyclogger

Reasons (based on the campaign):

infostealer
exfiltration-credentials
exfiltration-browser-data

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

b43b78466684583bb9a90ced072406566a033523e3b0d2b9032a4dae763ac84c

f6272f7350d759c72adcbef07c1c85f6ddbcc1c0ea5f3fe5c47e36bcc38eeb86

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

Campaign

2026-02-pycloggerRLMA-2026-00624

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter
ReversingLabs · finder

Detect & block this

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