# MAL-2026-17639: Malicious code in lore-cs (PyPI)


- **Type:** Malicious package
- **Package:** `lore-cs` (PyPI)
- **Published:** 6 Oct 2026

## What is MAL-2026-17639?

MAL-2026-17639 is a malicious package in lore-cs, published on 6 Oct 2026. 

### Official description

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

## What should I do about MAL-2026-17639?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17639 is a malicious package: lore-cs (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17639/ (Markdown: https://insights.sbomify.com/MAL-2026-17639/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17639

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17639/
Summaries are generated and may contain mistakes; the official description above is the record.