Which versions of enc30685 are malicious?

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

How do I remediate enc30685 if I installed it?

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

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

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

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

Malicious package

enc30685RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7667

Immediate action

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

gem uninstall enc30685

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1b514a4f1342680fbc2f4ec13863bafc800ea4fdab99978feab1a4017c20b415

61a298688da0993c7ce5beec6490a911178e426a778213671461b05ea71c4d9c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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