Which versions of sm8235yapr are malicious?

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

How do I remediate sm8235yapr if I installed it?

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

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

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

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

Malicious package

sm8235yaprRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8807

Immediate action

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

gem uninstall sm8235yapr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d09aa432ab0473148cd3bea95d495e221a23640fbbdd2abc2ce772c31ea86511

c6257a5b13e36f4da6afdc95d52726f6b8b014b65f12787abe7cb257e68fc8f9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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