# MAL-2026-14349: Malicious code in boto4 (PyPI)


- **Type:** Malicious package
- **Package:** `boto4` (PyPI)
- **Published:** 21 Aug 2026

## What is MAL-2026-14349?

MAL-2026-14349 is a malicious package in boto4, published on 21 Aug 2026. 

### Official description

setup.py defines a custom setuptools install command (`EjecutaElf`) that base64-decodes a ~17MB embedded Linux ELF, writes it to /tmp/.systemd-helper, chmods 0755, and spawns it via subprocess.Popen during `pip install` on Linux. The tarball's importable package is a stub named `reques` with an empty __init__.py, and PKG-INFO advertises the project as an `HTTP library for humans (unofficial fix)` authored by `Anonymous`, requiring `requests` — a cover story that lures installers looking for a requests-related fix while the sole functional behavior is native-code execution on the installer's host at install time. Package name `boto4` and internal directory `reques` are lookalikes for boto3/requests.

During installation, package executes an embedded executable. The executable is capable of executing remote commands, establishing persistence, cryptomining, exfiltrating basic data, further network scanning and worm-style propagation. Actions are controlled via a Telegram bot.

---

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

Campaign: 2026-08-boto4

Reasons (based on the campaign):

 - cryptominer

 - worm

 - network-scan

 - The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

 - uses-telegram-bot

 - persistence

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

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

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

## Sources

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

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