Which versions of sm8285iqre are malicious?

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

How do I remediate sm8285iqre if I installed it?

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

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

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

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

Malicious package

sm8285iqreRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8817

Immediate action

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

gem uninstall sm8285iqre

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

acfb494429ed15b753d70f99d627c685af8454d130cfbe32d91b7a3820c38829

c3e74ea5cb8cd003651135e919b7d26d1be5114c1b1dcc4171821e487312c3f9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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