Which versions of promptflow-runtime are malicious?

The following PyPI versions of promptflow-runtime are flagged malicious: 99999999.0.0. Treat any of these as compromised.

How do I remediate promptflow-runtime if I installed it?

promptflow-runtime 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 promptflow-runtime — how do I know if it already compromised me?

If promptflow-runtime 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 promptflow-runtime part of a known attack campaign?

Yes — promptflow-runtime is associated with the 2026-04-promptflow-runtime 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 promptflow-runtime 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 promptflow-runtime (version 99999999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging promptflow-runtime across your stack and pipelines.

Malicious package

promptflow-runtimePyPI

Malicious code in promptflow-runtime (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3035

Immediate action

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

pip uninstall promptflow-runtime

What this malware does

During import, package collects basic information about the system, performs deep fingerprinting, and reports the data to the remote target. The package description attempts to build an impression it's an official package. The package name refers to the Docker image used by Microsoft's project: https://github.com/microsoft/promptflow/blob/6bfdec06ef16d875ca3b1744a1ef133f08c35340/docs/cloud/azureai/runtime-change-log.md?plain=1#L8

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

Campaign: 2026-04-promptflow-runtime

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
dependency-confusion
impersonation
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

1 flagged

99999999.0.0

Indicators of compromise (SHA-256)

5b42466489944454bbab304af3aa9869e3f0483cafc76b4da896f6512bb4c627

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 promptflow-runtime (version 99999999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging promptflow-runtime across your stack and pipelines.
If you installed it — respond
promptflow-runtime 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 promptflow-runtime 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 promptflow-runtime 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. promptflow-runtime on PyPI has been identified as a malicious package (version 99999999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-promptflow-runtime

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks promptflow-runtime-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