chore(ci): install datadog-ci from standalone binary instead of npm#25084
Draft
chore(ci): install datadog-ci from standalone binary instead of npm#25084
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pront
added
the
no-changelog
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Switches
datadog-ciinstallation fromnpm install -gto the standalone binary from GitHub Releases.Why
On 2026-03-30/31, the owner of the
axiosnpm package was compromised and malicious versions (1.14.1 and 0.30.4) were published containing a backdoor. See https://securitylabs.datadoghq.com/articles/axios-npm-supply-chain-compromise/Our CI installs
datadog-civiasudo npm install -g @datadog/datadog-ci@5.9.0. While the package version is pinned,npm install -gdoes not use a lockfile, so transitive dependencies (includingaxios) are resolved from the npm registry at install time. Any CI runner that executed this during the ~3.5 hour compromise window (2026-03-30 23:59 - 2026-03-31 03:25 UTC) could have pulled the malicious axios 1.14.1.Vector configuration
N/A - CI infrastructure change only.
How did you test this PR?
linux-x64,linux-arm64,darwin-x64,darwin-arm64) on the v5.9.0 release.maybe_install_npm_packageto skip re-download when the correct version is already cached.Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
🤖 Generated with Claude Code