Which versions of macklemore are malicious?

The following RubyGems versions of macklemore are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate macklemore if I installed it?

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

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

Yes — macklemore is associated with the RLMA-2025-06617, RLUA-2026-08583 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 macklemore across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for macklemore (version 1.0.1).

Malicious package

macklemoreRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

macklemore is a confirmed malicious RubyGems package (MAL-2025-192910) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in macklemore (RubyGems)

MAL-2025-192910

Immediate action

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

gem uninstall macklemore

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

ad866f010964bcbaedd0c808770dff6fe0bf529eb939f7fe11042321c2d44255

544de7578052b3474b60aa7574d7d1b11693c5d030c56b110752825d0c2f82dd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06617RLUA-2026-08583

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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