# MAL-2026-5272: Malicious code in goodoltoulas (PyPI)


- **Type:** Malicious package
- **Package:** `goodoltoulas` (PyPI)
- **Published:** 5 Jun 2026

## What is MAL-2026-5272?

MAL-2026-5272 is a malicious package in goodoltoulas, published on 5 Jun 2026. 

### Official description

On `pip install goodoltoulas`, setup.py unconditionally invokes setup_helper(), which downloads an opaque PE binary from an anonymous file-hosting service (storage.filebin.net) into C:\MALWARE_DELETE\main.exe and launches it via subprocess.Popen with CREATE_NEW_CONSOLE. There is no hash check, signature verification, or version pinning, and the host is unrelated to any package publisher. The library surface is a thin decoy: __init__.py forwards all attribute access to the `requests` module and the README advertises 'A simple request cloner for Python', providing cover for the install-time dropper. The drop path uses a self-incriminating directory name (C:\MALWARE_DELETE) and the response carries application/vnd.microsoft.portable-executable, confirming hostile intent. Any Windows installer running `pip install` will execute attacker-controlled code immediately.

During installation, package attempts to download and run an executable imitating malicious activity.

---

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: 2026-06-goodoldtoulas

Reasons (based on the campaign):

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

 - Downloads and executes a remote executable.

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

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

## Sources

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

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