NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

devplatform-spa-plugin-error-boundarynpm

Advisory published Updated

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)

MAL-2026-12766
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall devplatform-spa-plugin-error-boundary

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

1 flagged
35.4.6

Indicators of compromise (SHA-256)

282ec333b26c6283eb35916acab1db10c1362d296d0694b1548882c6e48c06be
52a6a2f9ca87decad3081725ea4293dce82d4c33a5afe1fdb9774776b95760be

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for devplatform-spa-plugin-error-boundary (version 35.4.6).

  2. 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.

  3. Did it already run?

    If devplatform-spa-plugin-error-boundary was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. devplatform-spa-plugin-error-boundary on npm has been identified as a malicious package (version 35.4.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015004GHSA-2557-fmc3-p2q7

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.

Explore

devplatform-spa-plugin-error-boundary (npm) malicious package — MAL-2026-12766 | O3 Security