Which versions of meridix are malicious?

The following npm versions of meridix are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate meridix if I installed it?

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

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

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

Search your lockfiles and build artifacts for meridix (version 999.0.0).

Malicious package

meridixnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in meridix (npm)

MAL-2026-1791

Immediate action

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

npm uninstall meridix

What this malware does

The package meridix was found to contain malicious code.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

02b8ee73b1e71aa11bcd6f5a05908b1f20e4db3f22285437271ccbe071a3253d

fee5912f22c9335dc691e9f3299a234417f7da5f5591924e8725053760bdb1b4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01428

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks meridix-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