Which versions of loggerex are malicious?

The following PyPI versions of loggerex are flagged malicious: 0.7.4, 0.7.5, 0.7.6. Treat any of these as compromised.

How do I remediate loggerex if I installed it?

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

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

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

Malicious package

loggerexPyPI

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

MAL-2025-191782

Immediate action

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

pip uninstall loggerex

What this malware does

It's a clone of "loguru" package which on import loads a second-stage script from loguru[.]guru. This makes a few checks and downloads the next stage, which is a code obfuscated with PyArmor with unclear behaviour.

The way the malicious code has been embedded could be called a "sophisticated" threat. The code is in the _logger.py in two places: the payload in L2242 as a long string constraint of only whitespaces, which are then transformed into bits and bytes, and later compiled and executed using "types.FunctionType" during initialisation of Core class.

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

Campaign: 2025-07-loquru

Reasons (based on the campaign):

typosquatting
obfuscation
clones-real-package
Downloads and executes a remote malicious script.

Malicious versions

3 flagged

0.7.40.7.50.7.6

Indicators of compromise (SHA-256)

3177e123c0555fb064b49aa1a070e749e5358b403c1ff877d70c756950f1b10d

7a27ca3e673f54a1e041d55e84b8a0e871239df2331c9a3fd1dbe20d1fa86f56

bcb53463166fd2bbbd8749db30bbc923dd192ac35348d123548a3ae4a64ac65d

77058b0f2ca4f22fe73bd6290136df9a273f4f9473dc8840146776b480d2026e

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

Campaign

2025-07-loquru

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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