devplatform-create-nx-spanpm
devplatform-create-nx-spa is a confirmed malicious npm package (MAL-2026-12707) that executes malicious code on install (malicious version 35.4.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-create-nx-spa (npm)
What this malware does
[email protected] ships an index.js main entry that silently require()s _bridge.js, which on load assembles Cloudflare Workers hostnames (oob-worker.cf10{0,1,2,3}-*.workers.dev) and a fallback DNS-TXT channel to *.dl.wel1.ru from split-string arrays joined at runtime, downloads an unsigned opaque binary, writes it to /var/tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755s it, and spawns it detached via spawn('/bin/sh', ['-c', <path>+' &'], {detached:true}) or spawn('cmd',...). The behavior is disguised as "analytics" and gated by an /tmp/.analytics_state timestamp. The child_process identifier and destination hostnames are assembled from 3-4 substring pieces (['oob-worker.cf103-070.wor','ke','rs.dev'].join(''), require('child_'+'process')) to defeat static string matching. The package presents itself as a lightweight Nx SPA scaffolder, but its main module's only load-time effect is to fetch and execute attacker-controlled code on the installer's host.
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 devplatform-create-nx-spa (version 35.4.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-create-nx-spa across your stack and pipelines.
If you installed it — respond
Remove devplatform-create-nx-spa 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 devplatform-create-nx-spa 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 devplatform-create-nx-spa 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 devplatform-create-nx-spa-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.