Which versions of sm8260dulk are malicious?

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

How do I remediate sm8260dulk if I installed it?

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

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

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

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

Malicious package

sm8260dulkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8812

Immediate action

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

gem uninstall sm8260dulk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c5ff3cb45c7559159123f87811f61d5942b8002f5ab0c2f15481ae91acc311c5

ea62f7ef34f8be913a02c90a1d86633f94b5b391ca9fe1f786269e5b61cc4bd3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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