Which versions of idleprobezz001177 are malicious?

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

How do I remediate idleprobezz001177 if I installed it?

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

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

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

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

Malicious package

idleprobezz001177RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7777

Immediate action

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

gem uninstall idleprobezz001177

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

27916b71a80090af95523220a70e5bb41806661db1ca50f8f425fab33804ea08

e4b4029db69f108f87a03c2b26094cae946af43bfec660552e5d35f96980c1ee

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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