Which versions of nf-iso-properties are malicious?

The following npm versions of nf-iso-properties are flagged malicious: 99.87.33. Treat any of these as compromised.

How do I remediate nf-iso-properties if I installed it?

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

If nf-iso-properties was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is nf-iso-properties part of a known attack campaign?

Yes — nf-iso-properties is associated with the GHSA-m83v-m4wm-vx4f, RLMA-2025-05434, RLUA-2025-05892 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 nf-iso-properties across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nf-iso-properties (version 99.87.33). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nf-iso-properties across your stack and pipelines.

Malicious package

nf-iso-propertiesnpm

nf-iso-properties is a confirmed malicious npm package (MAL-2025-48294) that executes malicious code on install (malicious version 99.87.33). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nf-iso-properties (npm)

MAL-2025-48294

Immediate action

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

npm uninstall nf-iso-properties

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.87.33

Indicators of compromise (SHA-256)

3931e1fe9c0a20bbdeb1e532f664f5e95b84b7c831342802db5c9d74795d0c6d

0bf996bea7addb23c6a698f2d52e16641c86eb2bce5562c77a17bca7df1c71e4

417fa540ecc8a8332a275b56eae3fc62f0dfb92020bb3efcfeb9483a856bb501

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nf-iso-properties (version 99.87.33). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nf-iso-properties across your stack and pipelines.
If you installed it — respond
Remove nf-iso-properties 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 nf-iso-properties was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks nf-iso-properties before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. nf-iso-properties on npm has been identified as a malicious package (version 99.87.33 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m83v-m4wm-vx4fRLMA-2025-05434RLUA-2025-05892

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks nf-iso-properties-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