Which versions of rubydocmeta1 are malicious?

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

How do I remediate rubydocmeta1 if I installed it?

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

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

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

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

Malicious package

rubydocmeta1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

rubydocmeta1 is a confirmed malicious RubyGems package (MAL-2026-8545) 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 rubydocmeta1 (RubyGems)

MAL-2026-8545

Immediate action

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

gem uninstall rubydocmeta1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7fe041e9d008ef4a36b79fa5f437d14e21c913d7cf177812fc70255aee064865

0ab22233a3b3a8950c92d736374eff1297c7784f36a2851660a288394d7e0b1a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for rubydocmeta1 (version 0.0.1).
If you installed it — respond
Remove rubydocmeta1 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 rubydocmeta1 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. rubydocmeta1 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-03196RLUA-2026-09088

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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