Which versions of kevin-thompson are malicious?

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

How do I remediate kevin-thompson if I installed it?

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

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

Yes — kevin-thompson is associated with the RLMA-2024-05758, RLUA-2024-10278, RLUA-2026-08243 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 kevin-thompson across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kevin-thompson (version 0.0.1).

Malicious package

kevin-thompsonRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

kevin-thompson is a confirmed malicious RubyGems package (MAL-2024-6952) 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 kevin-thompson (RubyGems)

MAL-2024-6952

Immediate action

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

gem uninstall kevin-thompson

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0e0444bb71ebf357bdbae69fb61e665ccd80065cea63b78f1d4fb16323132f54

99e750dd84b97d711add40f1096b7e6f948a2c2a6092916e455e3a69df37505a

468adecd4075c03a20c76677b171e0b4e5974b6194e7dbab4f0863d360573666

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for kevin-thompson (version 0.0.1).
If you installed it — respond
Remove kevin-thompson 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 kevin-thompson 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. kevin-thompson 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-2024-05758RLUA-2024-10278RLUA-2026-08243

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks kevin-thompson-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