Which versions of meet8402a are malicious?

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

How do I remediate meet8402a if I installed it?

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

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

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

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

Malicious package

meet8402aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8086

Immediate action

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

gem uninstall meet8402a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

04b6713599db06b879a993ba054eb9700a335ae29a9ee05004d12545f0c5bb2e

c48d65869a4926a06f59e06618ca6a9a320113a434999f52e78d2b25c9ea349a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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