# MAL-2026-14384: Malicious code in mlflow-otel-instrumentor (PyPI)


- **Type:** Malicious package
- **Package:** `mlflow-otel-instrumentor` (PyPI)
- **Published:** 23 Aug 2026

## What is MAL-2026-14384?

MAL-2026-14384 is a malicious package in mlflow-otel-instrumentor, published on 23 Aug 2026. 

### Official description

Package metadata impersonates AWS (author "AWS Support Team", email support@aws.com, homepage https://aws.amazon.com/) while the actual payload is fetched from an unrelated throwaway host. A custom setuptools install command writes a shell script into a temp directory that sleeps ~300 seconds, downloads an ELF binary from https://file.freestorage-04.bond/files/.../boto3_utils.elf via curl/wget, chmod +x's it, executes it detached via nohup as /tmp/systemd-helper, and then self-deletes the launcher script. Installing the package results in an unsigned, non-publisher ELF running as a background process on the installer's host with no relationship to the advertised AWS-support functionality.

During installation package downloads and executes an executable. The remote executable appears to be broken but suggests intentions for persistence via systemd services, cryptocurrency mining and propagating over the network.  Campaign shows some similarities with 2026-08-boto4

---

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

Campaign: 2026-08-mlflow-otel-instrumentor

Reasons (based on the campaign):

 - typosquatting

 - Downloads and executes a remote executable.

 - worm

 - persistence

 - network-scan

 - cryptominer

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

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

## Sources

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

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