Which versions of dlxprobe23 are malicious?

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

How do I remediate dlxprobe23 if I installed it?

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

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

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

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

Malicious package

dlxprobe23RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7633

Immediate action

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

gem uninstall dlxprobe23

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3a9f774877b3822047bc2d0321072db541f5e3709a3debbfc48cc2d514196409

6fb0638a7c1189958120456b53a6d0fcf9c6b50f497605083dc1cb6dcf21b876

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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