Which versions of monolith-twirp-copilot-registry are malicious?

The following RubyGems versions of monolith-twirp-copilot-registry are flagged malicious: 1.0.6. Treat any of these as compromised.

How do I remediate monolith-twirp-copilot-registry if I installed it?

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

If monolith-twirp-copilot-registry 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 monolith-twirp-copilot-registry across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for monolith-twirp-copilot-registry (version 1.0.6).

Malicious package

monolith-twirp-copilot-registryRubyGems

Advisory published Mar 27, 2026Updated Jul 23, 2026

monolith-twirp-copilot-registry is a confirmed malicious RubyGems package (MAL-2026-2266) that executes malicious code on install (malicious version 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in monolith-twirp-copilot-registry (RubyGems)

MAL-2026-2266

Immediate action

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

gem uninstall monolith-twirp-copilot-registry

What this malware does

The OpenSSF Package Analysis project identified 'monolith-twirp-copilot-registry' @ 1.0.6 (rubygems) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.6

Indicators of compromise (SHA-256)

d1eb9592b2f976d7d487d44c8f45592b2953e5f51edfeee7242e020dfb64176f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for monolith-twirp-copilot-registry (version 1.0.6).
If you installed it — respond
Remove monolith-twirp-copilot-registry 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 monolith-twirp-copilot-registry 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. monolith-twirp-copilot-registry on RubyGems has been identified as a malicious package (version 1.0.6 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 monolith-twirp-copilot-registry-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