Which versions of dlxprobe18 are malicious?

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

How do I remediate dlxprobe18 if I installed it?

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

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

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

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

Malicious package

dlxprobe18RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7627

Immediate action

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

gem uninstall dlxprobe18

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cd6b17a7965bee9d5d04ae06160cca349ba08e353f48f3b3a0d60c41a403ceef

e97e91d4ae4e9d3e556f5581948308a059679110ce753e365c41be7568fcc24d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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