Which versions of newrubylogger are malicious?

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

How do I remediate newrubylogger if I installed it?

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

If newrubylogger 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.

How do I find newrubylogger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for newrubylogger (version 99.9.1).

Malicious package

newrubyloggerRubyGems

Advisory published Feb 23, 2026Updated Jul 23, 2026

newrubylogger is a confirmed malicious RubyGems package (MAL-2026-1002) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in newrubylogger (RubyGems)

MAL-2026-1002

Immediate action

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

gem uninstall newrubylogger

What this malware does

The OpenSSF Package Analysis project identified 'newrubylogger' @ 99.9.1 (rubygems) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

d10fd2e8adb621ac6bb3b4cd31357213d90dd17f27cd1f01d5e8e7138686d7c2

Detection & response playbook

Malicious package

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

Credits

OpenSSF: Package Analysis · finder

Detect & block this

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