Which versions of metrify-node are malicious?

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

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

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

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

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

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

Malicious package

metrify-nodenpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

metrify-node is a confirmed malicious npm package (MAL-2026-2780) 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 metrify-node (npm)

MAL-2026-2780

Immediate action

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

npm uninstall metrify-node

What this malware does

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

Malicious versions

1 flagged

2.4.5

Indicators of compromise (SHA-256)

0fbe497d88bdc295956fee7c68235569163330b9b86ba9ef0a69aa13b820ce8f

14ba3eb49fcfc273f48441c970f14f2eff02a5c141b9a7c60cb935bc7895a940

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for metrify-node (version 2.4.5).
If you installed it — respond
Remove metrify-node 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 metrify-node 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. metrify-node 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-01991

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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