Which versions of meet8178a are malicious?

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

How do I remediate meet8178a if I installed it?

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

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

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

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

Malicious package

meet8178aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8084

Immediate action

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

gem uninstall meet8178a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1c44892e9f781c74b6e6f8d096487ceb702918de41b77335881de2420edeca83

5a00802d79f2810b3b0c419b5ca5fb7bdf30f62ee7bde9ca0a2f099ffb07fa57

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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