Which versions of enc30809 are malicious?

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

How do I remediate enc30809 if I installed it?

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

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

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

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

Malicious package

enc30809RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7671

Immediate action

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

gem uninstall enc30809

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

601999e0ee5b9de73c64d961d184b5eedf636854af514c672b1159f62bec0984

158efedbb37a791ab19d930b66178d2eb2ded13102a44b7e7e3928ba4ad79413

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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