Which versions of node-metrica are malicious?

The following npm versions of node-metrica are flagged malicious: 2.4.5. Treat any of these as compromised.

How do I remediate node-metrica if I installed it?

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

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

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

Search your lockfiles and build artifacts for node-metrica (version 2.4.5).

Malicious package

node-metricanpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

node-metrica is a confirmed malicious npm package (MAL-2026-2786) that executes malicious code on install (malicious version 2.4.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-metrica (npm)

MAL-2026-2786

Immediate action

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

npm uninstall node-metrica

What this malware does

The package node-metrica was found to contain malicious code.

Malicious versions

1 flagged

2.4.5

Indicators of compromise (SHA-256)

26aacaacaae68536576c7ad2b493e9b1c59ca33fe9b9afdd3a1334331cbd4075

383d9c273b104a26749eb5f7f5ceb732c407b08002e5017418eb19563cb5b536

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02003

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks node-metrica-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