Which versions of slwfossil7565 are malicious?

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

How do I remediate slwfossil7565 if I installed it?

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

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

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

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

Malicious package

slwfossil7565RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8794

Immediate action

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

gem uninstall slwfossil7565

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

4e5b21d4676c02687c77a757a8923bcc5998f7e251c65f6c90cfe669db303a51

ab0707ed0321c98537265e198d9324877f06132f1c00dd4c4edac2c71eb52f9c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slwfossil7565 (version 0.0.2).
If you installed it — respond
Remove slwfossil7565 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 slwfossil7565 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. slwfossil7565 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-03445RLUA-2026-09343

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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