Which versions of sm8230mamd are malicious?

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

How do I remediate sm8230mamd if I installed it?

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

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

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

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

Malicious package

sm8230mamdRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8806

Immediate action

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

gem uninstall sm8230mamd

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

48eebd663bfc02ad454b46314c61327e67655d77971379c34a0d64a4304ad326

741ebe28bc6f23472efa50cb2de847451a3bda58b5c2696b17bda21b1a5c08dd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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