Which versions of dlxprobe6 are malicious?

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

How do I remediate dlxprobe6 if I installed it?

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

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

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

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

Malicious package

dlxprobe6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7637

Immediate action

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

gem uninstall dlxprobe6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6187ea8a9336ff2b66ee3ceefb9af1cbc198f068c248e2d5d7b6d22a0e352863

6fb1328ba4c78ce996b3303c83e6efca014644e2f549d53561ecdcc8f6061d1c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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