Which versions of dlxprobe9 are malicious?

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

How do I remediate dlxprobe9 if I installed it?

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

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

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

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

Malicious package

dlxprobe9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7640

Immediate action

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

gem uninstall dlxprobe9

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0d564841db46abd3033297c893b08c0c2142bd2a8e7967051ac509bec38810e2

878d0cb05baaed3396a97a5f86203c328a7cf62d213eede5c9aeaba1b9375146

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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