Which versions of dlxprobe7 are malicious?

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

How do I remediate dlxprobe7 if I installed it?

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

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

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

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

Malicious package

dlxprobe7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7638

Immediate action

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

gem uninstall dlxprobe7

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

57d6f6832a15bc47013edfecfbda408422a59bddb742699b8ab7979fa3d90bfe

7fec8d0e99617ac19db5a7be28d9d0439f9c600ee80d7b852849b2d2707c2067

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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