Which versions of zmeta7631 are malicious?

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

How do I remediate zmeta7631 if I installed it?

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

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

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

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

Malicious package

zmeta7631RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9663

Immediate action

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

gem uninstall zmeta7631

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

eef4acbc8664985db83950d43095dafba9cb38c095d42fdcecf1645f161847d3

efc4950f7929d613e081b7d4824dc46f66e5b21f441b6102a849b9753fc00494

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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