Which versions of dlxprobe16 are malicious?

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

How do I remediate dlxprobe16 if I installed it?

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

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

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

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

Malicious package

dlxprobe16RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7625

Immediate action

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

gem uninstall dlxprobe16

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a640bccbcfe2e38cb194b065816f9907de7f90f4f1d53d933bce4cb6cce39372

0d5c280d5b216158eb5a0722fb4fbfe762f6ec122693f3cac8974a2254cfdfc6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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