devplatform-spa-testingnpm
Advisory published Updated
devplatform-spa-testing is a confirmed malicious npm package (MAL-2026-12784) that opens a backdoor for remote access (malicious version 35.8.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-spa-testing (npm)
What this malware does
On require('devplatform-spa-testing'), index.js loads _platform.js which selects a platform-specific endpoint, retrieves a payload over HTTPS from string-concatenated oob-worker.cf*.workers.dev hostnames (with a DNS-TXT-chunked base64 fallback via sdk.dl.wel1.ru), writes it to /tmp or %TEMP% under a disguised name (.cache_<rand> on POSIX or dotnet_diag_<rand>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd. The C2 hostnames are assembled by joining fragments (e.g. ['oob-w','orker.cf102-','baf.worke','rs.d','ev'].join('')) to defeat plain string scanning, and the dropper filenames plus cover-story comments about telemetry opt-out mask the behavior. The fetched bytes are attacker-controlled and executed on the installer's machine at import time.
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
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for devplatform-spa-testing (version 35.8.6).
If you installed it — respond
devplatform-spa-testing establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If devplatform-spa-testing 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks devplatform-spa-testing-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.