Which versions of sm8240rjol are malicious?

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

How do I remediate sm8240rjol if I installed it?

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

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

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

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

Malicious package

sm8240rjolRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8808

Immediate action

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

gem uninstall sm8240rjol

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

69b1942bc1566ba02eafab4c3aa3e1c0c34d2f31d6bc7c3d50c5ea2147a2e630

bf56a268235febd5d60a61be1bd9c03d2fe2763d7b8a8f6d0781d8caa140a92d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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