Which versions of ezfnfix are malicious?

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

How do I remediate ezfnfix if I installed it?

ezfnfix is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed ezfnfix — how do I know if it already compromised me?

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

Yes — ezfnfix is associated with the IN-MAL-2026-015808 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 ezfnfix 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 ezfnfix (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ezfnfix across your stack and pipelines.

Malicious package

ezfnfixnpm

ezfnfix is a confirmed malicious npm package (MAL-2026-13344) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ezfnfix (npm)

MAL-2026-13344

Immediate action

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

npm uninstall ezfnfix

What this malware does

On Windows, npm install ezfnfix automatically executes a bundled Windows PE binary via a postinstall hook. package.json declares scripts.postinstall = "node postinstall.js", and postinstall.js enumerates bin/*.exe and runs the first entry with execFileSync. The shipped bin/ezfn.exe is a ~114 KB VB.NET executable whose metadata contains identifiers consistent with a remote-access trojan and infostealer: Telegram bot exfiltration primitives (SendBot, ChatID), socket C2 (ClientSocket, ConnectServer, ActivatePong), a spreading routine (Spread), AV/Defender-exclusion logic (Exclusion), webcam access (avicap32.dll), WMI-based host enumeration (ManagementObjectSearcher, get_UserName, get_MachineName, get_OSFullName, get_TotalPhysicalMemory), registry persistence handles (RegistryKey, CurrentUser), symmetric cryptography primitives, and WebClient/DownloadString network fetch. The binary ships with no source, no build step, no hash or signature verification, and no purpose consistent with the package name. Installing on Windows results in immediate execution of the RAT against the installer's host, exfiltrating identity and system information via Telegram/socket channels and providing persistent remote access.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3a5bd6bf9cde5f28e20365db24b77ca15226b5248a3be482e30c45d98259b301

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ezfnfix (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ezfnfix across your stack and pipelines.
If you installed it — respond
ezfnfix is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ezfnfix 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 ezfnfix 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. ezfnfix 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

IN-MAL-2026-015808

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ezfnfix-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database