twork-mf-e2e-nitronpm
twork-mf-e2e-nitro is a confirmed malicious npm package (MAL-2026-12303) that executes malicious code on install (malicious version 20.8.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-mf-e2e-nitro (npm)
What this malware does
On require of the package, index.js loads compat.js which reconstructs Cloudflare workers.dev hostnames via split-string array concatenation (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT fallback under *.dl.well1.site, downloads a platform-specific binary via https.get, writes it to /var/tmp or the Windows temp directory under a masquerading name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start. Misleading comments referencing an 'Analytics SDK', a 'DISABLE_TELEMETRY opt-out', and a 'SHA-256 integrity check' are present in the source; no such integrity check is implemented. A second copy of the same write-chmod-spawn dropper is staged in lib/telemetry.js (81 KB), reachable via dynamic loading. The require("child_"+"process") and fs["chmod"+"Sync"] patterns further evidence deliberate string-level evasion.
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 twork-mf-e2e-nitro (version 20.8.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twork-mf-e2e-nitro across your stack and pipelines.
If you installed it — respond
Remove twork-mf-e2e-nitro 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 twork-mf-e2e-nitro 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 twork-mf-e2e-nitro 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 twork-mf-e2e-nitro-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.