Which versions of newslambprint1 are malicious?

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

How do I remediate newslambprint1 if I installed it?

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

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

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

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

Malicious package

newslambprint1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8121

Immediate action

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

gem uninstall newslambprint1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

551021ed84f90476e12451fa3fd41138eb8d10c9f00caa86fa49622b8648c050

c0e4517596b7aadc8ffaba63371d15271915a85690a0c9fe08cc8c489ad92a1f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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