Which versions of swlicdoca are malicious?

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

How do I remediate swlicdoca if I installed it?

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

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

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

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

Malicious package

swlicdocaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8940

Immediate action

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

gem uninstall swlicdoca

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dc6a9fa49e1c4463d1e408bf7f21277b96d60d88b2c3ed3da294246e27a21c12

2b1be3226ee6a25779869c3915f08fef76463535bf8ea8ee1c9221b9a8d1e08c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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