Which versions of mlflow-otel-instrumentor are malicious?

The following PyPI versions of mlflow-otel-instrumentor are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate mlflow-otel-instrumentor if I installed it?

mlflow-otel-instrumentor is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed mlflow-otel-instrumentor — how do I know if it already compromised me?

If mlflow-otel-instrumentor was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is mlflow-otel-instrumentor part of a known attack campaign?

Yes — mlflow-otel-instrumentor is associated with the 2026-08-mlflow-otel-instrumentor campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find mlflow-otel-instrumentor across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mlflow-otel-instrumentor (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mlflow-otel-instrumentor across your stack and pipelines.

Malicious package

mlflow-otel-instrumentorPyPI

mlflow-otel-instrumentor is a confirmed malicious PyPI package (MAL-2026-14384) that steals credentials and exfiltrates sensitive data (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mlflow-otel-instrumentor (PyPI)

MAL-2026-14384

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall mlflow-otel-instrumentor

What this malware does

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

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

596b37cefcfec9359e87bfd5663962ce80c05c8851c4f894b6b4ea294ee0bbfd

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mlflow-otel-instrumentor (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mlflow-otel-instrumentor across your stack and pipelines.
If you installed it — respond
mlflow-otel-instrumentor is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If mlflow-otel-instrumentor was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks mlflow-otel-instrumentor before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. mlflow-otel-instrumentor on PyPI has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-08-mlflow-otel-instrumentor

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks mlflow-otel-instrumentor-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database