Which versions of loguru-utf8 are malicious?

The following PyPI versions of loguru-utf8 are flagged malicious: 0.7.3, 0.7.4. Treat any of these as compromised.

How do I remediate loguru-utf8 if I installed it?

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

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

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

Malicious package

loguru-utf8PyPI

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

MAL-2025-192435

Immediate action

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

pip uninstall loguru-utf8

What this malware does

Package clones a popular package (loguru, jsonschema, ...). While it claims to have some additional features, the real change is an added compiled native library which is silently loaded in the background during the importing of the module. The exact behavior is unknown, but the binary is obfuscated

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

Campaign: 2025-12-loguru-utf8

Reasons (based on the campaign):

clones-real-package
obfuscation
typosquatting
native-extension

Malicious versions

2 flagged

0.7.30.7.4

Indicators of compromise (SHA-256)

ed36240df4acc0e07b3e2a542c261afb54c1fe8466cf496057926b6c2dca3841

e20933ac001bbe12fd7962f9e12208f3224c836f3deba7669a649165232e0b78

24dffce422aaa4e56a42c75c1dbe6cc6b8601fce2a450f244290e0c49100ece3

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

Campaign

2025-12-loguru-utf8

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks loguru-utf8-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