Which versions of dlxprobe13 are malicious?

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

How do I remediate dlxprobe13 if I installed it?

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

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

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

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

Malicious package

dlxprobe13RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

dlxprobe13 is a confirmed malicious RubyGems package (MAL-2026-7622) 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 dlxprobe13 (RubyGems)

MAL-2026-7622

Immediate action

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

gem uninstall dlxprobe13

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a3a95ab614167b433520ac1cfff1c157676c3ac2ad270b04b1dfcea00655dca3

98efca107c34eb8670c7fb250d9a4ae57d2437a9c00b5366472583b4a411436c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dlxprobe13 (version 0.0.1).
If you installed it — respond
Remove dlxprobe13 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 dlxprobe13 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. dlxprobe13 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-02273RLUA-2026-07986

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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