devplatform-spa-plugin-error-boundarynpm
devplatform-spa-plugin-error-boundary is a confirmed malicious npm package (MAL-2026-12766) that executes malicious code on install (malicious version 35.4.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-spa-plugin-error-boundary (npm)
What this malware does
The package's main index.js unconditionally requires./ext, which runs at load time and fetches a per-platform binary over HTTPS from string-concatenation-obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev). If HTTPS fails, ext.js falls back to a DNS TXT covert channel under *.dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), querying c.<domain> for a chunk count then 0.<domain>, 1.<domain>,... and base64-decoding the concatenation into a binary. The fetched bytes are written to a randomly-named file in the temp directory (masquerading as.cache<hex>, dotnet_diag<hex>.exe, analytics_state), chmod'd 0755, and spawned detached via /bin/sh -c or cmd /c start /b. There is no version pinning, hash verification, or publisher-owned CDN, and the package's stated purpose (an SPA error-boundary component) has no legitimate reason to fetch and execute a native binary. Endpoint hostnames are assembled from split array literals at runtime to defeat static string scanning. Loading this package causes arbitrary attacker-controlled code to run on the installer's host.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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-error-boundary (version 35.4.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-error-boundary across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-plugin-error-boundary 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-error-boundary 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-error-boundary 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-error-boundary-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.