Which versions of johnny_five are malicious?

The following RubyGems versions of johnny_five are flagged malicious: 0.8.0, 0.9.4, 1.0.0, 1.0.9, 1.1.0, 1.1.0.1, 1.1.1, 1.2.0, 1.2.1, 1.98.0, 1.99.0, 9.0.0, 9.1.0, 9.1.1. Treat any of these as compromised.

How do I remediate johnny_five if I installed it?

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

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

Yes — johnny_five is associated with the RLMA-2024-10277, RLUA-2024-11215, RLUA-2026-08241 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 johnny_five across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for johnny_five (14 malicious versions).

Malicious package

johnny_fiveRubyGems

johnny_five is a confirmed malicious RubyGems package (MAL-2024-10221) that executes malicious code on install (malicious versions 0.8.0, 0.9.4, 1.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in johnny_five (RubyGems)

MAL-2024-10221

Immediate action

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

gem uninstall johnny_five

Malicious versions

14 flagged

0.8.00.9.41.0.01.0.91.1.01.1.0.11.1.11.2.01.2.11.98.01.99.09.0.09.1.09.1.1

Indicators of compromise (SHA-256)

6ba9da2aa8f85947a7aa1ceca4552388a358ea653ab8e2a00e4b9672b3091aec

da15e05b0a1012fae25629e943a3d6d4b6288edf237dbc6bce1ce31a9299e19b

61941265b2c993eb0f23877fc848f8174fdb2cc3ccf74ddc1085d33bf800240e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for johnny_five (14 malicious versions).
If you installed it — respond
Remove johnny_five 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 johnny_five 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. johnny_five on RubyGems has been identified as a malicious package (versions 0.8.0, 0.9.4, 1.0.0, 1.0.9, 1.1.0, 1.1.0.1, 1.1.1, 1.2.0, and 6 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-10277RLUA-2024-11215RLUA-2026-08241

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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