Which versions of xlambpdfconv are malicious?

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

How do I remediate xlambpdfconv if I installed it?

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

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

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

Search your lockfiles and build artifacts for xlambpdfconv (version 0.0.1).

Malicious package

xlambpdfconvRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

xlambpdfconv is a confirmed malicious RubyGems package (MAL-2026-9532) 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 xlambpdfconv (RubyGems)

MAL-2026-9532

Immediate action

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

gem uninstall xlambpdfconv

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5dafa55153425157b27ebe62eeaf389899ec98d4d84716fc91cdd24922702c53

c7374af3364283a12cf2fe2f32366d555a2a8d280be706163e70c8ec6b5ae102

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for xlambpdfconv (version 0.0.1).
If you installed it — respond
Remove xlambpdfconv 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 xlambpdfconv 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. xlambpdfconv 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-2026-04183RLUA-2026-10116

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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