Which versions of std5805a are malicious?

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

How do I remediate std5805a if I installed it?

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

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

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

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

Malicious package

std5805aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8903

Immediate action

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

gem uninstall std5805a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8c606228a710d6d31c83a9ca6b61a40402313f9130aa4e08949703fea11e5f1c

3d1b4793edda807393181e1f28f3278d9508e528cae003d333822ab4f926a425

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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