Which versions of sm8220jarc are malicious?

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

How do I remediate sm8220jarc if I installed it?

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

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

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

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

Malicious package

sm8220jarcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8804

Immediate action

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

gem uninstall sm8220jarc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

70cd94444755cecf38caec6f99af1464a9b09435dccd989fcca57706adf4f41e

047190bdb353cd1c71f4b6ac76bf327bf09dc52711f9bb90e6870229308266e9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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