Which versions of cdd-plugin-for-datawarrior are malicious?

The following npm versions of cdd-plugin-for-datawarrior are flagged malicious: 8.0.0. Treat any of these as compromised.

How do I remediate cdd-plugin-for-datawarrior if I installed it?

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

If cdd-plugin-for-datawarrior 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 cdd-plugin-for-datawarrior part of a known attack campaign?

Yes — cdd-plugin-for-datawarrior is associated with the GHSA-45h7-9rxv-wjrr, RLMA-2026-01141 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 cdd-plugin-for-datawarrior 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 cdd-plugin-for-datawarrior (version 8.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cdd-plugin-for-datawarrior across your stack and pipelines.

Malicious package

cdd-plugin-for-datawarriornpm

Malicious code in cdd-plugin-for-datawarrior (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192966

Immediate action

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

npm uninstall cdd-plugin-for-datawarrior

What this malware does

The package cdd-plugin-for-datawarrior 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.

Malicious versions

1 flagged

8.0.0

Indicators of compromise (SHA-256)

65d3ce36ff38a0a1cbc3bfabb49f3917c076b4aae6b8c061af9d926a487f881b

5ab7ca6ae4de6f4b1898f1507f69f89459ab40983852692e28a6b599f9e2318f

c0324f3eec886a924b211face9266a93f343a0d72a73a542793230ea529f31b1

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 cdd-plugin-for-datawarrior (version 8.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cdd-plugin-for-datawarrior across your stack and pipelines.
If you installed it — respond
Remove cdd-plugin-for-datawarrior 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 cdd-plugin-for-datawarrior 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 cdd-plugin-for-datawarrior 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. cdd-plugin-for-datawarrior on npm has been identified as a malicious package (version 8.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-45h7-9rxv-wjrrRLMA-2026-01141

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks cdd-plugin-for-datawarrior-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