Which versions of opentelemetry-exporter-otlp-http are malicious?

The following RubyGems versions of opentelemetry-exporter-otlp-http are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4. Treat any of these as compromised.

How do I remediate opentelemetry-exporter-otlp-http if I installed it?

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

If opentelemetry-exporter-otlp-http 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 opentelemetry-exporter-otlp-http part of a known attack campaign?

Yes — opentelemetry-exporter-otlp-http is associated with the RLMA-2026-05729 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 opentelemetry-exporter-otlp-http across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for opentelemetry-exporter-otlp-http (5 malicious versions).

Malicious package

opentelemetry-exporter-otlp-httpRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

opentelemetry-exporter-otlp-http is a confirmed malicious RubyGems package (MAL-2026-15763) that executes malicious code on install (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in opentelemetry-exporter-otlp-http (RubyGems)

MAL-2026-15763

Immediate action

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

gem uninstall opentelemetry-exporter-otlp-http

Malicious versions

5 flagged

0.1.00.1.10.1.20.1.30.1.4

Indicators of compromise (SHA-256)

5a6ce95eeffddc734befd760635ec5bff50cbb4c87f631fdec17f4f15fb87072

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for opentelemetry-exporter-otlp-http (5 malicious versions).
If you installed it — respond
Remove opentelemetry-exporter-otlp-http 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 opentelemetry-exporter-otlp-http 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. opentelemetry-exporter-otlp-http on RubyGems has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05729

Credits

ReversingLabs · finder

Detect & block this

O3 blocks opentelemetry-exporter-otlp-http-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