Which versions of sm8205canb are malicious?

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

How do I remediate sm8205canb if I installed it?

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

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

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

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

Malicious package

sm8205canbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8801

Immediate action

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

gem uninstall sm8205canb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

afd5e753a6ed4e9fab9e0b52b25fdfafe907cf3ab8dda13d1d7f98be7c20181a

cc47af95295c1024b3537ac64de338ba531c8eca39b56160f7c6ab3d02c536ad

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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