Which versions of swcal01 are malicious?

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

How do I remediate swcal01 if I installed it?

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

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

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

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

Malicious package

swcal01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8920

Immediate action

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

gem uninstall swcal01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d985b8476a4ba2afb0e5eacaf0f3839cee52f54f1bd115b6d71907a512e350e1

078fe286d3e518de39faa00fd37e51d2c25b0dbf591da2e287c1e544d9c8c7bd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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