Which versions of lore-cs are malicious?

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

How do I remediate lore-cs if I installed it?

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

If lore-cs was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is lore-cs part of a known attack campaign?

Yes — lore-cs is associated with the GENERIC-hackerone-bugbounty, IN-MAL-2026-021129 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 lore-cs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lore-cs (version 1.0.0).

Malicious package

lore-csPyPI

Advisory published Oct 6, 2026Updated Oct 8, 2026

lore-cs is a confirmed malicious PyPI package (MAL-2026-17639) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lore-cs (PyPI)

MAL-2026-17639

Immediate action

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

pip uninstall lore-cs

What this malware does

lore-cs 1.0.0 executes an outbound HTTP POST both from setup.py (at install time) and from lore_cs/init.py (at import time) to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc over plaintext HTTP. The payload includes the installer's hostname, install path, current working directory, and package name. The import-time beacon fires on every import, so the behavior also triggers in environments where pip build isolation would otherwise contain setup.py side effects. The destination is a hardcoded author-controlled bare IP not configured by the installer, and the package self-labels as a dependency-confusion canary while performing unauthenticated host-identifier collection against anyone who installs or imports it.

During installation or import, the package exfiltrates basic information in a dependency confusion attempt. The user identifies themselves as a HackerOne user abusing the PyPI for the purpose of a bug bounty program.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-hackerone-bugbounty

Reasons (based on the campaign):

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ae8b741b7c90400c3a5f4ba13533b1a6a75134f768934834b591c8df23eecb83

f84e496d81c3e514ec784db2d5996a9015fa9f01f50cb75a99011eb348b2aa07

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for lore-cs (version 1.0.0).
If you installed it — respond
lore-cs 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 lore-cs was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. lore-cs 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

GENERIC-hackerone-bugbountyIN-MAL-2026-021129

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks lore-cs-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

Explore

All malware advisories How O3 detects malware Vulnerability database