# MAL-2026-927: Malicious code in polyclawd (PyPI)


- **Type:** Malicious package
- **Package:** `polyclawd` (PyPI)
- **Published:** 16 Feb 2026

## What is MAL-2026-927?

MAL-2026-927 is a malicious package in polyclawd, published on 16 Feb 2026. 

### Official description

The package is prepared to download a hardcoded executable and save it in %LOCALAPPDATA% under a very generic name, clearly aiming to hide its existence. Code is also prepared to alter MarkOfTheWeb, start as admin and run the executable, but in analyzed versions this behavior was not triggered in any existing code path. The downloading will happen e.g. on starting the declared command line.

Remote executables are standalone applications or installators, including ClickOnce installators. However, in the analysis attempts, none of them showed clear malicious behavior, in most cases crashing during the analysis. Captured network traffic shows communication with the remote server and likely expects the URL of the next stage, which was not delivered from the server. Additionally, the code embeds a separate path for execution on non-Windows machines. It attempts to execute a remote script, but in analyzed versions, the domain used is already suspended and not reachable. 

In newer packages the remote code is another downloader, which then downloads a PyInstaller-packed executable that just calls back home but has no more functionality.

---

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-02-magichat

Reasons (based on the campaign):

 - Downloads and executes a remote executable.

 - other

 - typosquatting

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

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

## Sources

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

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