Which versions of sm8210ubba are malicious?

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

How do I remediate sm8210ubba if I installed it?

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

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

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

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

Malicious package

sm8210ubbaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8802

Immediate action

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

gem uninstall sm8210ubba

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

18d42c069a50c0799ae43b78ee351c02e4b161b5ff529ba6a27d8b014e8c26b8

88ffd7f512c959a2e4ee98452aa28583b86f6bab319418887af56aab5e539f5d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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