# MAL-2026-12190: Malicious code in retracfix (npm)


- **Type:** Malicious package
- **Package:** `retracfix` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-12190?

MAL-2026-12190 is a malicious package in retracfix, published on 5 Aug 2026. 

### Official description

The npm package retracfix@1.0.0 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.

## What should I do about MAL-2026-12190?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-12190 is a malicious package: retracfix (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-12190/ (Markdown: https://insights.sbomify.com/MAL-2026-12190/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-12190

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-12190/
Summaries are generated and may contain mistakes; the official description above is the record.