Which versions of dlxprobe2 are malicious?

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

How do I remediate dlxprobe2 if I installed it?

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

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

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

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

Malicious package

dlxprobe2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7629

Immediate action

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

gem uninstall dlxprobe2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

175210732cdd52e8b36c3d617677e6c193759d6d8e61d559b9bb0dc33e0a4581

756bd941c9c11801ca4e2a780a033c655430a06a7675976b85e49a869fbfe5da

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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