devplatform-spa-plugin-modulenpm
devplatform-spa-plugin-module is a confirmed malicious npm package (MAL-2026-12771) that executes malicious code on install (malicious version 35.7.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-spa-plugin-module (npm)
What this malware does
On require of the package's main entry, polyfill.js executes init() which reconstructs destination hostnames via array-join string splits (e.g. ["oob-worke","r.cf100-416.worker","s.","dev"].join("")), selects a platform-specific endpoint, downloads an opaque binary via https.get from one of several Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev, cf101-adf, cf102-baf, cf103-070.workers.dev), writes the payload to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods it 0755, and spawns it detached via spawn("/bin/sh",["-c",fp+" &"],{detached:true,stdio:"ignore"}).unref() or spawn("cmd",...). If HTTPS retrieval fails, a fallback path resolves TXT records at c.<discovery-domain> and iteratively at N.<discovery-domain> under *.dl.wel1.ru (sdk/ext/pkg/net subdomains), base64-concatenates the chunks, and treats the result as the executable payload. Host reconstruction, disguised file names, staging in temp directories, detached execution, and a DNS TXT covert-channel fallback together constitute a fully productionized install-time dropper delivering arbitrary attacker code to any machine that installs or requires this package.
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-spa-plugin-module (version 35.7.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-module across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-plugin-module 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-spa-plugin-module 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-spa-plugin-module 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-spa-plugin-module-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.