# MAL-2026-17881: Malicious code in py-sock2 (PyPI)


- **Type:** Malicious package
- **Package:** `py-sock2` (PyPI)
- **Published:** 15 Oct 2026

## What is MAL-2026-17881?

MAL-2026-17881 is a malicious package in py-sock2, published on 15 Oct 2026. 

### Official description

Importing py-sock2's `agentaix` module downloads a mutable Python file from `https://raw.githubusercontent.com/anonrider404/pypl/refs/heads/main/readme.txt` to a temporary `.py` file and launches it without a visible console on Windows. Its `agentaix` console entry point imports the module. The remote file's Git history contains a Windows remote file management client that registers persistence through an HKCU Run entry, polls `https://googleforum.pythonanywhere.com` for commands, and supports file upload, download, deletion, and command execution. An earlier remote-file revision is byte-identical to the `readme.txt` payload reported in MAL-2026-17752 (`agentaix`); the 39,931-byte `agentaix/gui.py` is also byte-identical across that package and py-sock2. The remote file is mutable; its contents at the time of any particular victim import and actual execution on victim systems have not been established.

The package installs a persistent job that allows the attacker for exfiltrating files and executing remote code on the victim's machine.

---

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

Campaign: 2026-10-agentaix

Reasons (based on the campaign):

 - files-exfiltration

 - peristence-autorun

 - The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

 - rat

 - persistence

 - Downloads and executes a remote malicious script.

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

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

## Sources

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

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