Which versions of dlxprobe12 are malicious?

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

How do I remediate dlxprobe12 if I installed it?

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

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

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

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

Malicious package

dlxprobe12RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7621

Immediate action

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

gem uninstall dlxprobe12

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

86e3c092eed48d54a4b459a18a84dc75dd57634761c6c1b3109e179cdd651569

1f7a57f584c70bd218c5ab3608ce377f6f10adbaf40c6d37bb2bb5849080acee

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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