Which versions of flashsimplelogger are malicious?

The following PyPI versions of flashsimplelogger are flagged malicious: 0.1.0, 0.2.0. Treat any of these as compromised.

How do I remediate flashsimplelogger if I installed it?

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

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

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

Malicious package

flashsimpleloggerPyPI

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

MAL-2025-191729

Immediate action

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

pip uninstall flashsimplelogger

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

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

4e15e4d836902748ddc1299d65d490003096ba69cc7a42f9aa54a08616c99616

8c4753ee44e481f1f689cfaeddcddaef8dcdf86fbb1db19b3fe0acc2fadac305

29b910f6bee20818c26414d261dfd8f0c9a0e6cf428265e3497a31ec16302b94

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 flashsimplelogger (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flashsimplelogger across your stack and pipelines.
If you installed it — respond
flashsimplelogger 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 flashsimplelogger 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 flashsimplelogger 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. flashsimplelogger on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0 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 flashsimplelogger-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