Which versions of pagerbot are malicious?

The following RubyGems versions of pagerbot are flagged malicious: 4.9.9, 5.9.9. Treat any of these as compromised.

How do I remediate pagerbot if I installed it?

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

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

Yes — pagerbot is associated with the RLMA-2024-05808, RLUA-2024-10329, RLUA-2026-08931 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 pagerbot across my projects, lockfiles, and CI pipelines?

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

Malicious package

pagerbotRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

pagerbot is a confirmed malicious RubyGems package (MAL-2024-7002) that executes malicious code on install (malicious versions 4.9.9, 5.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pagerbot (RubyGems)

MAL-2024-7002

Immediate action

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

gem uninstall pagerbot

Malicious versions

2 flagged

4.9.95.9.9

Indicators of compromise (SHA-256)

c5c15b1828e2ee7b5cce908a66ca95de04e23128b2891036ccab9737e170d0a6

19040b48401fb349739c250570042cdaa48120cb5a140aac0faab493511fc561

2fa9cd6f03f6426510ba302fbe277052ed6da39ee38dc947f6ac606e24603853

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05808RLUA-2024-10329RLUA-2026-08931

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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