Which versions of swcalcald are malicious?

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

How do I remediate swcalcald if I installed it?

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

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

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

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

Malicious package

swcalcaldRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8924

Immediate action

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

gem uninstall swcalcald

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0256a6802b9bc4beee07c84a70addccbd324baaa43dade4f681d5ed2b76eae9d

fa2f28eceb3df75fb5c68bfd6b38e256c55294d45aee600b54227e22b1231b59

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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