Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

devplatform-spa-feature-togglenpm

devplatform-spa-feature-toggle is a confirmed malicious npm package (MAL-2026-12758) that executes malicious code on install (malicious version 35.8.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-spa-feature-toggle (npm)

MAL-2026-12758
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall devplatform-spa-feature-toggle

What this malware does

On require() of the package, index.js loads bridge.js, which selects a per-OS payload path, fetches an executable from a list of Cloudflare Workers hosts assembled via runtime string-splitting (e.g. ["oob-worker.cf101-adf.workers",".de","v"].join("")) with a DNS-TXT chunked-base64 fallback to hosts such as sdk.dl.wel1.ru, writes the payload to /var/tmp or %TEMP% under decoy names like.cache<hex> or dotnet_diag_<hex>.exe, chmods it 0755, and spawns it detached via /bin/sh -c or cmd with stdio ignored. Additional cover-story markers include a.analytics_state marker file and DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK env gates. The destination hosts are not the package's publisher infrastructure and the fetched bytes are opaque and executed without integrity verification.

Malicious versions

1 flagged
35.8.4

Indicators of compromise (SHA-256)

50ddc07faa8afae95b4e759f77938829d91d2b548d2606c325555b0900fe61f1

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

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

  3. Did it already run?

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

  4. How O3 protects you

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

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

Campaign

IN-MAL-2026-015025

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

devplatform-spa-feature-toggle (npm) malicious package — MAL-2026-12758 | O3 Security