Which versions of sm8290nhgm are malicious?

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

How do I remediate sm8290nhgm if I installed it?

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

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

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

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

Malicious package

sm8290nhgmRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8818

Immediate action

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

gem uninstall sm8290nhgm

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

85bb0886e796b8b3955f4279897895560f10f964c37f7c8ce44464dcd60001bf

63dd93e89567e0fdcc224f5f2d46fd5c92a127cb5d2b493d4d8b75b52b780591

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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