Which versions of @covance/cvd3 are malicious?

The following npm versions of @covance/cvd3 are flagged malicious: 1.2.194, 1.2.195, 1.2.196, 1.2.197, 1.2.198. Treat any of these as compromised.

How do I remediate @covance/cvd3 if I installed it?

Remove @covance/cvd3 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 @covance/cvd3 — how do I know if it already compromised me?

If @covance/cvd3 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 @covance/cvd3 part of a known attack campaign?

Yes — @covance/cvd3 is associated with the RLMA-2025-05235, RLUA-2025-05648 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 @covance/cvd3 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @covance/cvd3 (5 malicious versions).

Malicious package

@covance/cvd3npm

Advisory published Sep 23, 2025Updated Dec 2, 2025

@covance/cvd3 is a confirmed malicious npm package (MAL-2025-47573) that executes malicious code on install (malicious versions 1.2.194, 1.2.195, 1.2.196…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @covance/cvd3 (npm)

MAL-2025-47573

Immediate action

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

npm uninstall @covance/cvd3

What this malware does

The package communicates with a domain associated with malicious activity.

Malicious versions

5 flagged

1.2.1941.2.1951.2.1961.2.1971.2.198

Indicators of compromise (SHA-256)

b5d44a58a4f83e42fd020a18b38b7e89ad51952653902401fbfbabfa7413deed

77b67c134899f53ebeb0ed7af758e80995bdb604da70b74d51832350ef7b4b10

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @covance/cvd3 (5 malicious versions).
If you installed it — respond
Remove @covance/cvd3 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 @covance/cvd3 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. @covance/cvd3 on npm has been identified as a malicious package (versions 1.2.194, 1.2.195, 1.2.196, 1.2.197, 1.2.198 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05235RLUA-2025-05648

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @covance/cvd3-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