Which versions of sm8255oilg are malicious?

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

How do I remediate sm8255oilg if I installed it?

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

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

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

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

Malicious package

sm8255oilgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8811

Immediate action

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

gem uninstall sm8255oilg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8492d171c3281da6b85af2a18ebd434e5d8023938fec341a35ca35e66f238a80

dcbde3f74fc4f52d4ee455729bee2f2d70ca3ab3537b7c0f9a8ab1b9a9eeaece

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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