Which versions of enc30778 are malicious?

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

How do I remediate enc30778 if I installed it?

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

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

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

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

Malicious package

enc30778RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7670

Immediate action

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

gem uninstall enc30778

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1a785e1d14ef917c92d1e8f1db443d675b5c452c30c7aa69aacc5c8bdeb84dff

1a0746d0a5eeae181c871fec957dbf4bbf02e58765352a6ea97c155f4a01bff9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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