Which versions of enc30582 are malicious?

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

How do I remediate enc30582 if I installed it?

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

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

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

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

Malicious package

enc30582RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7664

Immediate action

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

gem uninstall enc30582

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a20078c4254ca1a98657ffbb14c6c8933a596d31e690e150b5815e3b446af1dd

2c2d2c3d7815a6075506bc969ca76e0d48c3aa43ed0efee72cb751c064983384

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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