Which versions of sm8200qkel are malicious?

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

How do I remediate sm8200qkel if I installed it?

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

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

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

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

Malicious package

sm8200qkelRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8800

Immediate action

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

gem uninstall sm8200qkel

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7cec51ae18dd8c8ad03f9f223fdbcdf2bb6781a52c59f7900ec8880c318ab965

9eba6a6a1145c50a4d9f727107374c27c03deccb442936e3571c4d3dbc2c29d8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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