Which versions of meet8405a are malicious?

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

How do I remediate meet8405a if I installed it?

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

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

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

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

Malicious package

meet8405aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8087

Immediate action

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

gem uninstall meet8405a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3089e700727621e088fda5796d6731a9c4b1eedaccbe17687641ad8700734c96

be9eb3ba1deb529d751bdee60aee494ab63de4e9ed042af89c0f1df52f68f269

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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