# MAL-2026-5321: Malicious code in orchestr8-platform (PyPI)


- **Type:** Malicious package
- **Package:** `orchestr8-platform` (PyPI)
- **Published:** 6 Jun 2026
- **Also known as:** PYSEC-2026-1073

## What is MAL-2026-5321?

MAL-2026-5321 is a malicious package in orchestr8-platform, published on 6 Jun 2026. 

### Official description

The package was found to contain malicious code or consuming dependency that contains malicious code

Versions 3.3.2 were compromised.

Compromised packages start an obfuscated infostealer. The infostealer is a heavily obfuscated JavaScript code executed using Bun runtime on Python startup. It collectes all kinds of sensitive data, including API keys, credentials to package repositories, cryptocurrency assets, password manager data. Infostealer actively queries online services to collect additional secrets as well as attempts to gain persistence and spread further by publishing infected packages using collected credentials. Data are exfiltrated likely using Github. The code seems to threaten to wipe the user's data if it detects invalid GitHub tokens. Cleanup should be done with caution.

It seems to be related to the recent Mini Shai Hulud campaign.

---

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

Campaign: 2026-06-compr-woodpecker

Reasons (based on the campaign):

 - compromised-package

 - exfiltration-env-variables

 - exfiltration-cloud-tokens

 - exfiltration-credentials

 - abuses-pth

 - obfuscation

 - infostealer

 - The package contains code to detect if it is running in a sandbox environment.

 - exfiltration-crypto

 - files-exfiltration

 - destructive-actions

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

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

## Sources

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

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