Which versions of log-guru are malicious?

The following PyPI versions of log-guru are flagged malicious: 0.7.8. Treat any of these as compromised.

How do I remediate log-guru if I installed it?

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

If log-guru was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is log-guru part of a known attack campaign?

Yes — log-guru is associated with the 2026-07-tennacity 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 log-guru across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for log-guru (version 0.7.8).

Malicious package

log-guruPyPI

Advisory published Jul 15, 2026Updated Jul 19, 2026

log-guru is a confirmed malicious PyPI package (MAL-2026-10688) that steals credentials and exfiltrates sensitive data (malicious version 0.7.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in log-guru (PyPI)

MAL-2026-10688

Immediate action

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

pip uninstall log-guru

What this malware does

The typosquatted package installs a Mythic/Poseidon C2 framework beacon and ensures persistence. After installation, the beacon communicates with C2 on wegoexchange[.]site for further commands.

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

Campaign: 2026-07-tennacity

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote executable.
The package contains code to detect if it is running in a sandbox environment.
malware
persistence

Malicious versions

1 flagged

0.7.8

Indicators of compromise (SHA-256)

6da98c6d79df38328235bb1df969316bd484b2a02594f8656772cd9a1e48f16b

a2c5f8cae152b81854a314f285ce2a072e7b9bf72c298dfb41c9db9960b45280

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for log-guru (version 0.7.8).
If you installed it — respond
log-guru 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 log-guru was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. log-guru on PyPI has been identified as a malicious package (version 0.7.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-07-tennacity

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks log-guru-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

Explore

All malware advisories How O3 detects malware Vulnerability database