Which versions of jekyll-rp-logs are malicious?

The following RubyGems versions of jekyll-rp-logs are flagged malicious: 0.5.0. Treat any of these as compromised.

How do I remediate jekyll-rp-logs if I installed it?

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

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

Yes — jekyll-rp-logs is associated with the RLMA-2024-05755, RLUA-2024-10274, RLUA-2026-08238 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 jekyll-rp-logs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jekyll-rp-logs (version 0.5.0).

Malicious package

jekyll-rp-logsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

jekyll-rp-logs is a confirmed malicious RubyGems package (MAL-2024-6949) that executes malicious code on install (malicious version 0.5.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jekyll-rp-logs (RubyGems)

MAL-2024-6949

Immediate action

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

gem uninstall jekyll-rp-logs

Malicious versions

1 flagged

0.5.0

Indicators of compromise (SHA-256)

d8f1635ec97a4bf186799de678a51bf9e70be84d06f12ea0a081c799b9f3ff8d

0191f33f2124597a32ad1705dfe74e6bb1a6f298951eb637c4c063574d474fdc

25f0e32e9ea155321b2a490617b93de4a930277d3a9fc4a164d411cab0fde4c2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05755RLUA-2024-10274RLUA-2026-08238

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks jekyll-rp-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