Which versions of slwhg1453 are malicious?

The following RubyGems versions of slwhg1453 are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate slwhg1453 if I installed it?

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

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

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

Search your lockfiles and build artifacts for slwhg1453 (version 0.0.2).

Malicious package

slwhg1453RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

slwhg1453 is a confirmed malicious RubyGems package (MAL-2026-8796) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in slwhg1453 (RubyGems)

MAL-2026-8796

Immediate action

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

gem uninstall slwhg1453

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

66c6a6a2ccc85495a5c444fa1002084ce70d35eadcb4ee438249d662a148759a

ccff60690fc24e5c44d0a6a07d9bf9faf763788199b1429e0a0c117747f09469

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slwhg1453 (version 0.0.2).
If you installed it — respond
Remove slwhg1453 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 slwhg1453 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. slwhg1453 on RubyGems has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03447RLUA-2026-09345

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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