Which versions of devplatform-spa-plugin-notifier are malicious?

The following npm versions of devplatform-spa-plugin-notifier are flagged malicious: 35.5.7. Treat any of these as compromised.

How do I remediate devplatform-spa-plugin-notifier if I installed it?

Remove devplatform-spa-plugin-notifier 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.

I already installed devplatform-spa-plugin-notifier — how do I know if it already compromised me?

If devplatform-spa-plugin-notifier 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.

Is devplatform-spa-plugin-notifier part of a known attack campaign?

Yes — devplatform-spa-plugin-notifier is associated with the IN-MAL-2026-015002 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find devplatform-spa-plugin-notifier across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-spa-plugin-notifier (version 35.5.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-notifier across your stack and pipelines.

Malicious package

devplatform-spa-plugin-notifiernpm

devplatform-spa-plugin-notifier is a confirmed malicious npm package (MAL-2026-12773) that executes malicious code on install (malicious version 35.5.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-spa-plugin-notifier (npm)

MAL-2026-12773

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall devplatform-spa-plugin-notifier

What this malware does

On module load, index.js requires bootstrap.js which selects a platform-specific asset, downloads an opaque binary from hardcoded Cloudflare Workers subdomains (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS TXT chunked-base64 fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes it to a disguised temp path (names such as dotnet_diag* and.cache_*), chmods it 0755 on Unix, and spawns it detached via /bin/sh -c or cmd /c start. Hostnames are assembled at runtime by joining fragmented substrings to defeat string search, and telemetry-opt-out variable names (analytics_state, DISABLE_TELEMETRY) are used as cover. No hash or signature verification is performed, and the destinations bear no relationship to a 'spa plugin notifier'.

Malicious versions

1 flagged

35.5.7

Indicators of compromise (SHA-256)

877337509f36ab52fcfb93d1dc48d77439a5154d077fc047b7263265cfb71468

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-spa-plugin-notifier (version 35.5.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-notifier across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-plugin-notifier 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-notifier 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-notifier 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

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

Campaign

IN-MAL-2026-015002

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-spa-plugin-notifier-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database