Which versions of wcalamp are malicious?

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

How do I remediate wcalamp if I installed it?

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

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

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

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

Malicious package

wcalampRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9320

Immediate action

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

gem uninstall wcalamp

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5d0735d501d5fd626f667901acdfa0a794f9a96d8fcefbf13f914f2cb0e1b930

921e0f7afb2ed370ef9f67fbc93433bc84fe9034fbd650dbcb391ff6fea99000

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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