Which versions of lcalprobe are malicious?

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

How do I remediate lcalprobe if I installed it?

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

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

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

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

Malicious package

lcalprobeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7965

Immediate action

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

gem uninstall lcalprobe

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f0364b38069ffe798fd144a559f00ea61ea30a82766cd0f7ff2a9c2c2511ec7c

0ee18c274d7c4fe8ec407996a74b3f273dbe2a76cae0ab7021c3037c88b618b9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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