Which versions of swlicsuba are malicious?

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

How do I remediate swlicsuba if I installed it?

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

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

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

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

Malicious package

swlicsubaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8944

Immediate action

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

gem uninstall swlicsuba

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9b34976a9b30a673bfdb359aa55cbae3798be22fbea688f2769a09b5a0499f11

55f55cab046ebda8608427fdefe42fb4f54e732baaf94b6ca9ea335741823684

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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