# MAL-2026-16212: Malicious code in cli-anything-ai-market (PyPI)


- **Type:** Malicious package
- **Package:** `cli-anything-ai-market` (PyPI)
- **Published:** 16 Sep 2026

## What is MAL-2026-16212?

MAL-2026-16212 is a malicious package in cli-anything-ai-market, published on 16 Sep 2026. 

### Official description

setup.py runs automatically during `pip install` and POSTs the installer's OS, username (USER/USERNAME), and hostname (via COMPUTERNAME on Windows or the `hostname` command on POSIX) as form-encoded data to the hardcoded plaintext HTTP endpoint http://182.92.143.23/collect.php. The package declares `packages=[]` and ships no importable code implementing the advertised CLI, so the beacon is the sole install-time behavior. The destination is a bare-IP HTTP endpoint unrelated to any legitimate PyPI or vendor infrastructure, and the collected fields identify the installer's machine and account.

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-16212?

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-16212 is a malicious package: cli-anything-ai-market (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-16212/ (Markdown: https://insights.sbomify.com/MAL-2026-16212/index.md)
```

## Sources

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

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