Which versions of sprobehgz are malicious?

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

How do I remediate sprobehgz if I installed it?

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

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

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

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

Malicious package

sprobehgzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8858

Immediate action

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

gem uninstall sprobehgz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

39e0e6149f8c46a413f06f4e0ce2b9997aa856150a1c90f8cafea41d7ea6710b

9c0b6bd6446bd6020c58e9cdb55639a5be199ee74fcc75afea8c537397fc7914

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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