Which versions of pdfmeno1 are malicious?

The following RubyGems versions of pdfmeno1 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pdfmeno1 if I installed it?

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

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

Yes — pdfmeno1 is associated with the RLMA-2026-03074, RLUA-2026-08944 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 pdfmeno1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pdfmeno1 (version 0.0.1).

Malicious package

pdfmeno1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in pdfmeno1 (RubyGems)

MAL-2026-8423

Immediate action

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

gem uninstall pdfmeno1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7fc0d86df7bea0b73874f9534b641b193a21baaf0dc4e08028667086b9b6b881

87061bd2c9ce46a875000f13a45e6c6021bcf26e702c2dbed076b1be0c08ad87

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03074RLUA-2026-08944

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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