Which versions of st3481c8 are malicious?

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

How do I remediate st3481c8 if I installed it?

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

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

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

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

Malicious package

st3481c8RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8898

Immediate action

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

gem uninstall st3481c8

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7a096e2ed4c1d697357df46c03b6ac3fbd9e75abef239b3dfc4a50cbaf69582d

d318598b84133c1dbc6d6807afc1250ec55bc695616ee0bc92ba62f79cf36913

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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