Which versions of dial-xl are malicious?

The following PyPI versions of dial-xl are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate dial-xl if I installed it?

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

If dial-xl 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.

Is dial-xl part of a known attack campaign?

Yes — dial-xl is associated with the RLMA-2025-02567, 2025-05-sl4x01 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 dial-xl across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dial-xl (version 0.0.1).

Part of a larger attack: 2025-05-sl4x01 published 8 malicious packages. See the full campaign →

Malicious package

dial-xlPyPI

Advisory published May 10, 2025Updated Dec 12, 2025

dial-xl is a confirmed malicious PyPI package (MAL-2025-3741) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dial-xl (PyPI)

MAL-2025-3741

Immediate action

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

pip uninstall dial-xl

What this malware does

Packages that seem to be created by a legit bug bounty hunter. Designed to look like created by different organisations, they contain a couple of data exfiltration (including all env variables) and potential remote code execution (though the URL seems not to serve any code).

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

Campaign: 2025-05-sl4x01

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.
exfiltration-env-variables
impersonation

The OpenSSF Package Analysis project identified 'dial-xl' @ 0.0.1 (pypi) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0febe63d78b1149e91af60c89ae73e492d43cb35f04dc6aaee2c4048987081a9

981cfe7e3f073f4617d3753692488e7d648638062ce86107e80053f7e42b27bf

bbee7f1a70bb8bd38a215ed7b6ed02042387824942682e3caedcd4dbe255ac29

129b71dc44955e560cd56ff53e0be19aced751699016fa96cb04ee75d2e76e3b

6998be6df530663dae02f1db20706272aefdaa812605fb740493e5f41d63c126

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for dial-xl (version 0.0.1).
If you installed it — respond
dial-xl 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 dial-xl 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. dial-xl on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-025672025-05-sl4x01

References

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks dial-xl-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