Which versions of datadog-checks-base are malicious?

The following npm versions of datadog-checks-base are flagged malicious: 50.0.0. Treat any of these as compromised.

How do I remediate datadog-checks-base if I installed it?

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

If datadog-checks-base was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is datadog-checks-base part of a known attack campaign?

Yes — datadog-checks-base is associated with the GHSA-6gq4-p64c-9qqf 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-checks-base across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for datadog-checks-base (version 50.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datadog-checks-base across your stack and pipelines.

Malicious package

datadog-checks-basenpm

Malicious code in datadog-checks-base (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192361

Immediate action

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

npm uninstall datadog-checks-base

What this malware does

The package datadog-checks-base was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'datadog-checks-base' @ 50.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

50.0.0

Indicators of compromise (SHA-256)

c0928a2f92beacda32023ac378b5df81feeffd91699903ea3500b46a6fcdefb9

365b7f484282733ddbd717a30ae576184245e59dd00c6d65414b2e0de045d2a5

0c81f3e37fe2d626410665826364d682e76edf32642b1cf36d4b12b987a9b102

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for datadog-checks-base (version 50.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datadog-checks-base across your stack and pipelines.
If you installed it — respond
Remove datadog-checks-base 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-checks-base was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks datadog-checks-base before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. datadog-checks-base on npm has been identified as a malicious package (version 50.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6gq4-p64c-9qqf

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks datadog-checks-base-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