Which versions of azureml-contrib-daskonbatch are malicious?

The following PyPI versions of azureml-contrib-daskonbatch are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate azureml-contrib-daskonbatch if I installed it?

Remove azureml-contrib-daskonbatch from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed azureml-contrib-daskonbatch — how do I know if it already compromised me?

If azureml-contrib-daskonbatch was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find azureml-contrib-daskonbatch across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for azureml-contrib-daskonbatch (version 1.0.0).

Malicious package

azureml-contrib-daskonbatchPyPI

azureml-contrib-daskonbatch is a confirmed malicious PyPI package (MAL-2023-8563) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in azureml-contrib-daskonbatch (PyPI)

MAL-2023-8563

Immediate action

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

pip uninstall azureml-contrib-daskonbatch

What this malware does

The OpenSSF Package Analysis project identified 'azureml-contrib-daskonbatch' @ 1.0.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

fbb97c227c663215810abd8867643e6709416bf4e16526391cc0c740f9dce047

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for azureml-contrib-daskonbatch (version 1.0.0).
If you installed it — respond
Remove azureml-contrib-daskonbatch from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If azureml-contrib-daskonbatch was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks azureml-contrib-daskonbatch-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database