Which versions of dlxprobe4 are malicious?

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

How do I remediate dlxprobe4 if I installed it?

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

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

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

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

Malicious package

dlxprobe4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7635

Immediate action

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

gem uninstall dlxprobe4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f0bf78802834af300c27f346a7f1b714aba8bb5f8a13ab90d2a94ba848c5560b

375c96f3643c14a5d105c840e0b4415842296c0cfea166ae086f6f502f55d0ba

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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