Which versions of dlxprobe22 are malicious?

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

How do I remediate dlxprobe22 if I installed it?

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

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

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

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

Malicious package

dlxprobe22RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7632

Immediate action

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

gem uninstall dlxprobe22

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8d769ff727f857477bf04c772fae58faedd0f713f3197271218bdd1751d4368e

bb123a04a25dcd5e82b600fed9f7b3e259ae3e21c0b2a50a21a4282edd0193e3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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