Which versions of swcalcala are malicious?

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

How do I remediate swcalcala if I installed it?

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

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

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

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

Malicious package

swcalcalaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8921

Immediate action

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

gem uninstall swcalcala

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4df68292c3ab1e4e7e2d5ad315499e2b4a0150eb6badeed2722b08b6d71066d4

cb666d863772c4f3fd2c24a58dd3fdaa551932e2afc4a32f496dbd33e2eafad8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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