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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for log-guru (version 0.7.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging log-guru across your stack and pipelines.

Malicious package

log-guruPyPI

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

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

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 log-guru (version 0.7.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging log-guru across your stack and pipelines.
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 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 log-guru 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. 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