Which versions of caljanzzjcq are malicious?

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

How do I remediate caljanzzjcq if I installed it?

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

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

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

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

Malicious package

caljanzzjcqRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

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

MAL-2026-7555

Immediate action

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

gem uninstall caljanzzjcq

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

96bbe25fc58402990c3951001a2552172536497a16240536d3c339dcd667094c

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

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