Which versions of enc30716 are malicious?

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

How do I remediate enc30716 if I installed it?

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

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

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

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

Malicious package

enc30716RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7668

Immediate action

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

gem uninstall enc30716

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d03031f31585645db58b7c2ef4ab1a5fabee45085912974d914f09d9ae03eb46

1d1e70ebcf7b5f5daee6ed617bb3d78110b6a0f2f1923a512e438d951fe37c7a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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