Which versions of codecoverage-tools are malicious?

The following npm versions of codecoverage-tools are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate codecoverage-tools if I installed it?

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

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

Yes — codecoverage-tools is associated with the RLMA-2026-01731 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 codecoverage-tools across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for codecoverage-tools (2 malicious versions).

Malicious package

codecoverage-toolsnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

codecoverage-tools is a confirmed malicious npm package (MAL-2026-2345) that executes malicious code on install (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in codecoverage-tools (npm)

MAL-2026-2345

Immediate action

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

npm uninstall codecoverage-tools

What this malware does

The package codecoverage-tools was found to contain malicious code.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

72c13dbd1852d2063bbfbbb0b2b78084c5a54d6a688adf9aeea196bc3936f3c6

77e8adaf551291b58aa99518bd0d9c4817709eb0e987acb0f318405926c8f6a1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for codecoverage-tools (2 malicious versions).
If you installed it — respond
Remove codecoverage-tools 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 codecoverage-tools 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. codecoverage-tools on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01731

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks codecoverage-tools-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