Which versions of retracfix are malicious?

The following npm versions of retracfix are flagged malicious: 1.0.0, 1.0.1, 1.0.3. Treat any of these as compromised.

How do I remediate retracfix if I installed it?

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

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

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

Malicious package

retracfixnpm

retracfix is a confirmed malicious npm package (MAL-2026-12190) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in retracfix (npm)

MAL-2026-12190

Immediate action

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

npm uninstall retracfix

What this malware does

The npm package [email protected] ships with no documented functionality (empty description, no README, no source, no dependencies) and consists only of postinstall.js plus a single Windows PE at bin/ezfn.exe. package.json declares scripts.postinstall='node postinstall.js' and os=['win32']; postinstall.js enumerates bin/ for any.exe and unconditionally runs it via execFileSync on Windows installs. The bundled ezfn.exe is a.NET assembly whose metadata contains the type/member signatures of a remote-control agent and infostealer: ClientSocket / ConnectServer / BeginConnect / isConnected / ActivatePong for a C2 socket; SendBot / ChatID plus WebClient.DownloadString for a Telegram-bot exfil/command channel; ManagementObjectSearcher with the strings 'Antivirus' and 'Exclusion' for AV enumeration and Defender-exclusion registration; avicap32.dll for webcam capture; Microsoft.Win32 RegistryKey / CurrentUser Run-key persistence; WindowsIdentity/WindowsPrincipal privilege checks; SymmetricAlgorithm CreateEncryptor/Decryptor, WriteAllBytes, GetTempPath, InstallDir/InstallStr/LoggerPath; and a 'Spread' routine. The package name plus the binary name 'ezfn' (Easy Fortnite) fit a gaming-cheat lure. Running npm install retracfix on Windows drops and launches this binary, handing persistent remote control of the installer's host to the operator.

Malicious versions

3 flagged

1.0.01.0.11.0.3

Indicators of compromise (SHA-256)

15feec56f800e0a120a9d99df2755c5ed5a92c42a0a0f4207bcb6304ae8a9fee

7656b934d52c542162613f35aa909400f46aa0dae186ef9d55667f048bdfdcd4

686e52b984e09e4bae909382a250db5acc1eda2e48a24c6af0083d15fdd82983

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 retracfix (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging retracfix across your stack and pipelines.
If you installed it — respond
retracfix 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 retracfix 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 retracfix 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. retracfix on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014476IN-MAL-2026-014473IN-MAL-2026-014474

References

Credits

Amazon Inspector · finder

Detect & block this

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