# MAL-2026-18122: Malicious code in moveworks-capi-starter (PyPI)


- **Type:** Malicious package
- **Package:** `moveworks-capi-starter` (PyPI)
- **Published:** 21 Oct 2026

## What is MAL-2026-18122?

MAL-2026-18122 is a malicious package in moveworks-capi-starter, published on 21 Oct 2026. 

### Official description

setup.py overrides the install command to collect the installer's hostname and resolved local IP address and POST them as JSON to the hardcoded URL https://webhook.site/17a7df2e-3d56-4c5a-b7a9-9a95fe58a533 during `pip install`, tagged with the package name and version. The beacon fires unconditionally at install time with no user disclosure or opt-out, and the package itself provides no documented functionality — the shipped code is a proof-of-concept beacon with placeholder author metadata. The exfiltrated data is limited to host identifiers (hostname, IP) rather than credentials, but the install-time network callback to a third-party collector enables correlation of installations with the operator of the webhook endpoint.

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

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-18122 is a malicious package: moveworks-capi-starter (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-18122/ (Markdown: https://insights.sbomify.com/MAL-2026-18122/index.md)
```

## Sources

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

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