Which versions of endosome are malicious?

The following RubyGems versions of endosome are flagged malicious: 22.55.0. Treat any of these as compromised.

How do I remediate endosome if I installed it?

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

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

Yes — endosome is associated with the RLMA-2024-05696, RLUA-2024-10215, RLUA-2026-08063 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 endosome across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for endosome (version 22.55.0).

Malicious package

endosomeRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

endosome is a confirmed malicious RubyGems package (MAL-2024-6890) that executes malicious code on install (malicious version 22.55.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in endosome (RubyGems)

MAL-2024-6890

Immediate action

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

gem uninstall endosome

Malicious versions

1 flagged

22.55.0

Indicators of compromise (SHA-256)

79ff07497e82e6ec5b9671462fe25310b123cf73faae2f57b8a7795d5c933e70

53f0536e7b5e90c66baa6b1afc4f52b0673914cb5bb10c1e78847db9f03a3208

8cbf2155c47bf3e2713ff2ae630dc5317d3ea0c8877ea077cb88bf6ab1f5c1ac

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for endosome (version 22.55.0).
If you installed it — respond
Remove endosome 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 endosome 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. endosome on RubyGems has been identified as a malicious package (version 22.55.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05696RLUA-2024-10215RLUA-2026-08063

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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