Which versions of hide-asset_logs are malicious?

The following RubyGems versions of hide-asset_logs are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hide-asset_logs if I installed it?

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

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

Yes — hide-asset_logs is associated with the RLMA-2024-05750, RLUA-2024-10269, RLUA-2026-08206 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 hide-asset_logs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hide-asset_logs (version 1.0.0).

Malicious package

hide-asset_logsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in hide-asset_logs (RubyGems)

MAL-2024-6944

Immediate action

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

gem uninstall hide-asset_logs

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

355db5a2ff6fc3b424311bb4a50b96e43f214d6310f6375dbb95c01456e66695

d64829daccb222676172f364d7ad41ca258639f287d8f718b60dc0b975f32879

49c14f768000d4223e55dd4c29ec7843df17f06a4ebf82ad23a71f6ae9850937

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05750RLUA-2024-10269RLUA-2026-08206

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks hide-asset_logs-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