Which versions of lambqueryjanabc are malicious?

The following RubyGems versions of lambqueryjanabc are flagged malicious: 0.0.2, 0.0.3, 0.0.4. Treat any of these as compromised.

How do I remediate lambqueryjanabc if I installed it?

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

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

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

Search your lockfiles and build artifacts for lambqueryjanabc (3 malicious versions).

Malicious package

lambqueryjanabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lambqueryjanabc is a confirmed malicious RubyGems package (MAL-2026-7842) that executes malicious code on install (malicious versions 0.0.2, 0.0.3, 0.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lambqueryjanabc (RubyGems)

MAL-2026-7842

Immediate action

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

gem uninstall lambqueryjanabc

Malicious versions

3 flagged

0.0.20.0.30.0.4

Indicators of compromise (SHA-256)

55f1130d4bd883f2f9bd56763e42d0cb5080d174a6f4aaa8985af22e41a362ef

a11bb2a290849ff10de423fe63f5368b0142b1e8534ad0f43fd910e4d5f15063

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lambqueryjanabc (3 malicious versions).
If you installed it — respond
Remove lambqueryjanabc 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 lambqueryjanabc 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. lambqueryjanabc on RubyGems has been identified as a malicious package (versions 0.0.2, 0.0.3, 0.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02493RLUA-2026-08308

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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