Which versions of newslambprint2 are malicious?

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

How do I remediate newslambprint2 if I installed it?

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

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

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

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

Malicious package

newslambprint2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8122

Immediate action

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

gem uninstall newslambprint2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

373f49c36dc673d607fdd113a49bc39242fc4d7728d1d812642071f6b2886866

979c568cce4ff432d5af664ebf9b43d228ffc02f55b858f0f7674872450d4359

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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