Which versions of enc30551 are malicious?

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

How do I remediate enc30551 if I installed it?

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

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

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

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

Malicious package

enc30551RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7663

Immediate action

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

gem uninstall enc30551

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1bcbfad8ea977e0ca3cc525fbb6cf819b02be08747b0c3079ac9fe8206e47646

41b85d561d32b7d13f5e13c0268f93299831c5231d46eb625e14bb8eb03becec

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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