Which versions of monolith-twirp-pullsd-repositories are malicious?

The following RubyGems versions of monolith-twirp-pullsd-repositories are flagged malicious: 1.0.10. Treat any of these as compromised.

How do I remediate monolith-twirp-pullsd-repositories if I installed it?

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

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

Search your lockfiles and build artifacts for monolith-twirp-pullsd-repositories (version 1.0.10).

Malicious package

monolith-twirp-pullsd-repositoriesRubyGems

Advisory published Mar 27, 2026Updated Jul 23, 2026

monolith-twirp-pullsd-repositories is a confirmed malicious RubyGems package (MAL-2026-2261) that executes malicious code on install (malicious version 1.0.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in monolith-twirp-pullsd-repositories (RubyGems)

MAL-2026-2261

Immediate action

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

gem uninstall monolith-twirp-pullsd-repositories

What this malware does

The OpenSSF Package Analysis project identified 'monolith-twirp-pullsd-repositories' @ 1.0.10 (rubygems) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.10

Indicators of compromise (SHA-256)

1c34eecc811d04d6583504ad631024a727df5e2107a1025a2786bf8a56a59d3a

Detection & response playbook

Malicious package

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