Which versions of ipherr are malicious?

The following npm versions of ipherr are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ipherr if I installed it?

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

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

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

Search your lockfiles and build artifacts for ipherr (version 1.0.0).

Malicious package

ipherrnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in ipherr (npm)

MAL-2026-1754

Immediate action

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

npm uninstall ipherr

What this malware does

The package ipherr was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1cdd2108e0d8b472f1967959a729dba9384e4bbfa2449cbe4dc1fcf39d2a2661

87963462e858ed616e53bff77bb6c78ef5cf38eccdde2b3bb08b13ad656e3645

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01361

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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