Which versions of dlxprobe0 are malicious?

The following RubyGems versions of dlxprobe0 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate dlxprobe0 if I installed it?

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

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

Yes — dlxprobe0 is associated with the RLMA-2026-02268, RLUA-2026-07981 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 dlxprobe0 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dlxprobe0 (version 0.0.1).

Malicious package

dlxprobe0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

dlxprobe0 is a confirmed malicious RubyGems package (MAL-2026-7617) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dlxprobe0 (RubyGems)

MAL-2026-7617

Immediate action

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

gem uninstall dlxprobe0

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

24e5c11662f59396f4e1298f07d1ecd68f970846da50842759bfdd960cc52319

030ec07d9eff260f2f03a98192698c69e07760812d28a0aab53429e3572b6938

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dlxprobe0 (version 0.0.1).
If you installed it — respond
Remove dlxprobe0 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 dlxprobe0 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. dlxprobe0 on RubyGems 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-2026-02268RLUA-2026-07981

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks dlxprobe0-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