devplatform-spa-plugin-feature-togglenpm
devplatform-spa-plugin-feature-toggle is a confirmed malicious npm package (MAL-2026-13546) that executes malicious code on install (malicious version 35.7.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-spa-plugin-feature-toggle (npm)
What this malware does
[email protected] executes attacker-controlled code on the installer's host at module import. The package's main entry loads support.js, which builds three hardcoded origins under .workers.dev (oob-worker.cf101/cf102/cf103-) by array-join concatenation to evade string scanning, with a DNS-TXT base64-chunked fallback under *.dl.wel1.ru. It downloads an OS-specific binary, writes it to /var/tmp/.cache<rnd> on Unix or %TEMP%/dotnet_diag_<rnd>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Cover-story naming ("analytics_state", "telemetry", "dotnet_diag") does not match the package's advertised feature-toggle purpose. A sibling file lib/telemetry.js contains a larger variant of the same drop-and-exec primitives framed as an "Analytics SDK", not currently reached from main. The destination origins are anonymous Cloudflare Workers and a DDNS-style host, not a publisher-owned domain, and the delivered payload is an opaque executable with no pinning or integrity check.
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-feature-toggle (version 35.7.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-feature-toggle across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-plugin-feature-toggle 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-feature-toggle 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-feature-toggle 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-feature-toggle-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.