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

The following RubyGems versions of monolith-twirp-pullsd-authorization are flagged malicious: 0.0.1, 1.0.4. Treat any of these as compromised.

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

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

If monolith-twirp-pullsd-authorization 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 monolith-twirp-pullsd-authorization part of a known attack campaign?

Yes — monolith-twirp-pullsd-authorization is associated with the RLMA-2026-02088, RLUA-2026-08598 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 monolith-twirp-pullsd-authorization across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for monolith-twirp-pullsd-authorization (2 malicious versions).

Malicious package

monolith-twirp-pullsd-authorizationRubyGems

Advisory published Apr 16, 2026Updated Sep 24, 2026

monolith-twirp-pullsd-authorization is a confirmed malicious RubyGems package (MAL-2026-2815) that executes malicious code on install (malicious versions 0.0.1, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-2815

Immediate action

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

gem uninstall monolith-twirp-pullsd-authorization

Malicious versions

2 flagged

0.0.11.0.4

Indicators of compromise (SHA-256)

1f54d69739767cd2cb2c05a7ff15be4dd2ac371a1e18ceb096ebb80f9077e9e0

904b17353ea7b28f271cf21d5a4c92bbadd772c824d005e739708f1cc4918481

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02088RLUA-2026-08598

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks monolith-twirp-pullsd-authorization-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