Which versions of enc30623 are malicious?

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

How do I remediate enc30623 if I installed it?

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

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

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

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

Malicious package

enc30623RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7665

Immediate action

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

gem uninstall enc30623

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8b4f11aea76025e34b7b589296a0720c3f9b6a1c981e80329cd5fed5939e31e5

46896625457b888e97c6ba959534fe63f66b41de148e0e4bf12ad1e937cd9b54

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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