Which versions of nicfv are malicious?

The following npm versions of nicfv are flagged malicious: 0.0.0, 0.0.0-0, 0.0.1. Treat any of these as compromised.

How do I remediate nicfv if I installed it?

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

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

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

Search your lockfiles and build artifacts for nicfv (3 malicious versions).

Malicious package

nicfvnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

nicfv is a confirmed malicious npm package (MAL-2026-1800) that executes malicious code on install (malicious versions 0.0.0, 0.0.0-0, 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nicfv (npm)

MAL-2026-1800

Immediate action

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

npm uninstall nicfv

What this malware does

The package nicfv was found to contain malicious code.

Malicious versions

3 flagged

0.0.00.0.0-00.0.1

Indicators of compromise (SHA-256)

eae4e758c9c5a91a5e6b15e06b26cdbd8609e6fb8ac1f96626356b9cdf0dc318

8ac5ed4e3707c6a712636b08407bd01f3a8d0c8b0f5733bca9034df7f0688503

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01453

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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