Which versions of doctolib are malicious?

The following RubyGems versions of doctolib are flagged malicious: 99.0.0, 99.0.1, 99.0.2, 99.0.3, 99.0.4. Treat any of these as compromised.

How do I remediate doctolib if I installed it?

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

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

Yes — doctolib is associated with the RLMA-2026-00951, RLUA-2026-08007 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 doctolib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for doctolib (5 malicious versions).

Malicious package

doctolibRubyGems

Advisory published Mar 18, 2026Updated Sep 24, 2026

doctolib is a confirmed malicious RubyGems package (MAL-2026-1915) that executes malicious code on install (malicious versions 99.0.0, 99.0.1, 99.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in doctolib (RubyGems)

MAL-2026-1915

Immediate action

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

gem uninstall doctolib

Malicious versions

5 flagged

99.0.099.0.199.0.299.0.399.0.4

Indicators of compromise (SHA-256)

27cfffb74315bae64d153fa214a3e4b62b069380055159e357ec1917a090d2f0

a07daf0d47e1e9c02b069e6d27b6e20758e4831379cd58d54f0e9d84c2c01576

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-00951RLUA-2026-08007

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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