Which versions of newlogger are malicious?

The following RubyGems versions of newlogger are flagged malicious: 99.9.1, 99.9.2. Treat any of these as compromised.

How do I remediate newlogger if I installed it?

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

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

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

Search your lockfiles and build artifacts for newlogger (2 malicious versions).

Malicious package

newloggerRubyGems

Advisory published Mar 18, 2026Updated Sep 24, 2026

newlogger is a confirmed malicious RubyGems package (MAL-2026-1918) that executes malicious code on install (malicious versions 99.9.1, 99.9.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in newlogger (RubyGems)

MAL-2026-1918

Immediate action

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

gem uninstall newlogger

Malicious versions

2 flagged

99.9.199.9.2

Indicators of compromise (SHA-256)

71d9c328f3961491511440bd5d4de1ac3fac2c915355b516574f1de4745e7945

6be461f4730e946e93d8638a9ef16d6b38f20d27dfc050d094b9aad4a25462af

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-00954RLUA-2026-08632

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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