Which versions of sprobefossilz are malicious?

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

How do I remediate sprobefossilz if I installed it?

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

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

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

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

Malicious package

sprobefossilzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8857

Immediate action

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

gem uninstall sprobefossilz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e6b5d910482985e71d263bcf44faa0d7060d0b7b6b6a72d1a1f30a692d6e7465

ad7c3a0f6b73773d417ad08e1e153f1cf3ed6bf5d632b3dcb828edddaa91e1a6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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