nxify-unicnpm
nxify-unic is a confirmed malicious npm package (MAL-2026-12069) that executes malicious code on install (malicious version 20.3.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in nxify-unic (npm)
What this malware does
On require('nxify-unic'), index.js loads shim.js which detects OS/architecture, assembles destination hostnames at runtime by string-splitting and Array.join('') (Cloudflare Workers hosts oob-worker.cf100-416.workers.dev / oob-worker.cf102-baf.workers.dev / oob-worker.cf101-adf.workers.dev and a DNS-TXT chunked-base64 fallback at *.dl.well1.site), downloads a platform-matched binary with no hash or signature verification, writes it to /var/tmp or %TEMP% under decoy filenames such as dotnet_diag<hex>.exe or.cache_<hex>, chmods it 0755, and spawns it detached via spawn('/bin/sh', ['-c', fp+' &']) or cmd.exe /c start /b. Destinations are anonymous workers.dev hosts unrelated to any declared publisher; endpoint strings are reconstructed at runtime to evade static analysis; a TTL cache and opt-out env-var gate re-execution. The behavior fires on module import, not at a user-invoked entry point.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nxify-unic (version 20.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nxify-unic across your stack and pipelines.
If you installed it — respond
Remove nxify-unic 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 nxify-unic 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 nxify-unic 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks nxify-unic-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.