Which versions of datadog-proxy are malicious?

The following RubyGems versions of datadog-proxy are flagged malicious: 0.0.6. Treat any of these as compromised.

How do I remediate datadog-proxy if I installed it?

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

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

Yes — datadog-proxy is associated with the RLMA-2024-05663, RLUA-2024-10182, RLUA-2026-07967 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 datadog-proxy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for datadog-proxy (version 0.0.6).

Malicious package

datadog-proxyRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

datadog-proxy is a confirmed malicious RubyGems package (MAL-2024-6857) that executes malicious code on install (malicious version 0.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in datadog-proxy (RubyGems)

MAL-2024-6857

Immediate action

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

gem uninstall datadog-proxy

Malicious versions

1 flagged

0.0.6

Indicators of compromise (SHA-256)

9863e1bd7618f259258384e1d0feab568aed2b5d0f57ae7898d5ccb9ca703b95

9b6eaccc251161f4f86dbe27143f31aaedcdbbf7613b7ac49dad647558b2eb28

a210c8f585f8dd1ff3e03289178e3d5ac75eb2313a6b81fea22b6a3927e81b2c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05663RLUA-2024-10182RLUA-2026-07967

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks datadog-proxy-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