Which versions of slvfossil308 are malicious?

The following RubyGems versions of slvfossil308 are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate slvfossil308 if I installed it?

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

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

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

Search your lockfiles and build artifacts for slvfossil308 (version 0.0.2).

Malicious package

slvfossil308RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

slvfossil308 is a confirmed malicious RubyGems package (MAL-2026-8791) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in slvfossil308 (RubyGems)

MAL-2026-8791

Immediate action

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

gem uninstall slvfossil308

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

4281fb84780d0ab5f890c250b7015c65323d5e04e8fa13c67cc11690bcb4e2b4

be3e85776a93e1f43fed17f24366cff4e7e69f085970d5f495219fe9a4ceee3e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slvfossil308 (version 0.0.2).
If you installed it — respond
Remove slvfossil308 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 slvfossil308 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. slvfossil308 on RubyGems has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03442RLUA-2026-09340

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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