Which versions of logghelper are malicious?

The following PyPI versions of logghelper are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate logghelper if I installed it?

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

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

Yes — logghelper is associated with the RLMA-2025-03632, 2025-07-logghelper, RLUA-2026-00476 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 logghelper 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 logghelper (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging logghelper across your stack and pipelines.

Malicious package

logghelperPyPI

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

MAL-2025-6538

Immediate action

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

pip uninstall logghelper

What this malware does

Code attempts to download and run malware, as well as keeps ability to execute files sent via Telegram C2 channel

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

Campaign: 2025-07-logghelper

Reasons (based on the campaign):

malware
infostealer
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

95dc49007971e90eb3fea73deb17542dfe6dd3b311c7498910299ef2a44a1065

653e827245df38ad57a6183cebfbf175cb68b166b03451a58ffcba38e54d9400

2a5f0848002e1727d885bdf20c39e4949fd9609a4df5164a8c42ccc870aa6736

f229b4e3e5216e3457a0b274f269964b652807c96405cea627ec8266316ed174

3d2e6d280b8b5061729c5d5efcb3bad8720677ee1b9bd028bb8808fee924046b

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

Campaign

RLMA-2025-036322025-07-logghelperRLUA-2026-00476

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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