Which versions of newslambcaljan6 are malicious?

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

How do I remediate newslambcaljan6 if I installed it?

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

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

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

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

Malicious package

newslambcaljan6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8120

Immediate action

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

gem uninstall newslambcaljan6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0af7cae9a87aeb5686e56be78af7c303bda2ad1ef3a1489bef8c620646d7b5b2

247598570284767950c035f236ee3aed779a8e727514caf78c941e971ca569cc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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