Which versions of dlxprobe19 are malicious?

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

How do I remediate dlxprobe19 if I installed it?

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

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

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

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

Malicious package

dlxprobe19RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7628

Immediate action

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

gem uninstall dlxprobe19

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e2d15d1497d97e96ed99e6cb0416bc7eef9a2a3cfc4ddf3b1024005b38bcc94a

4dee3fdd286280914d2671f8620be42f6da0e6c350e90c795145de853fd92386

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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