Which versions of logguru are malicious?

The following PyPI versions of logguru are flagged malicious: 0.7.3, 0.7.4, 0.7.5, 0.7.6, 0.7.7, 0.7.8. Treat any of these as compromised.

How do I remediate logguru if I installed it?

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

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

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

Malicious package

logguruPyPI

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

MAL-2025-191783

Immediate action

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

pip uninstall logguru

What this malware does

Malicious clone of a legitimate "loguru" package. There is added code to download and run an executable. Sandbox analysis reveals attempts to steal browsers data

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

Campaign: 2025-11-logguru

Reasons (based on the campaign):

clones-real-package
Downloads and executes a remote executable.
infostealer
typosquatting

Malicious versions

6 flagged

0.7.30.7.40.7.50.7.60.7.70.7.8

Indicators of compromise (SHA-256)

9e2280b7c5a7387c1ff2dc26dcead820f65ffddbd638f67fd653d55a70838232

64b91d48504c05711a759a1cb2a0bfd63650f47d05d04296bbea6269ed4229b4

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

Campaign

2025-11-logguru

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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