Which versions of has-changelogs are malicious?

The following RubyGems versions of has-changelogs are flagged malicious: 0.2.0. Treat any of these as compromised.

How do I remediate has-changelogs if I installed it?

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

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

Yes — has-changelogs is associated with the RLMA-2024-05746, RLUA-2024-10265, RLUA-2026-08178 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 has-changelogs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for has-changelogs (version 0.2.0).

Malicious package

has-changelogsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in has-changelogs (RubyGems)

MAL-2024-6940

Immediate action

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

gem uninstall has-changelogs

Malicious versions

1 flagged

0.2.0

Indicators of compromise (SHA-256)

868ec663ee29a7175a99bab332e6bcc358f78dc02d404d38bcc3c42dba5684dd

57652ff5cc9ef54c6b1c39e0cb902f11527fbc2000f6301ba9b7f5cf1c30d477

f266ab5d5d850ea971dd56aa963161132912a12ec56a05b8caa093656c53f5bb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05746RLUA-2024-10265RLUA-2026-08178

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks has-changelogs-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