# MAL-2026-18326: Malicious code in changes-lxc-wrapper (PyPI)


- **Type:** Malicious package
- **Package:** `changes-lxc-wrapper` (PyPI)
- **Published:** 26 Oct 2026

## What is MAL-2026-18326?

MAL-2026-18326 is a malicious package in changes-lxc-wrapper, published on 26 Oct 2026. 

### Official description

The distribution `changes-lxc-wrapper` ships a trivial package whose top-level import name is `ca_certificates`, creating a mismatch between the distribution name and the import namespace it occupies. The shipped `__init__.py` only defines a `__version__` constant and an `info()` function returning a placeholder string. There are no install or build hooks, no top-level import-time side effects, no subprocess or network activity, and no credential or filesystem access. Package metadata is placeholder (`Your Name` / `you@example.com`). No installer-side harmful behavior is present in the shipped code; the only concern is namespace shadowing on the common `ca_certificates` import name.

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

---

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-standard-pypi-install-pentest

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.

 - The package overrides the install command in setup.py to execute malicious code during installation.

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

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-18326 is a malicious package: changes-lxc-wrapper (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-18326/ (Markdown: https://insights.sbomify.com/MAL-2026-18326/index.md)
```

## Sources

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

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