Which versions of dlxprobe3 are malicious?

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

How do I remediate dlxprobe3 if I installed it?

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

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

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

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

Malicious package

dlxprobe3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7634

Immediate action

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

gem uninstall dlxprobe3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

502f2285cb5fdba1c83901625d69412ae98433017797855cace6f9a35a6c85f6

848f4565e6e8d6be22ca0e8cdb050a30a71f33125f9488b3fa1ee2cffc09e7a9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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