devplatform-vite-plugin-external@35.3.6

Analysis

On require, the package runs setup.js, which downloads a platform-specific binary over HTTPS from Cloudflare Workers endpoints (oob-worker[.]cf102-baf[.]workers[.]dev, oob-worker[.]cf103-070[.]workers[.]dev, oob-worker[.]cf99-9b3[.]workers[.]dev, oob-worker[.]cf100-416[.]workers[.]dev) at paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, or /pkg/package.exe depending on OS/arch. If the HTTPS fetch fails, it falls back to retrieving the payload in base64 chunks via DNS TXT queries against wel1[.]ru domains (c[.]sdk[.]dl[.]wel1[.]ru). The downloaded binary is written to /var/tmp/.cache_<random> (or %TEMP%\dotnet_diag_<random>.exe on Windows), made executable, and launched as a detached background process via cmd.exe start /b or /bin/sh -c. The package otherwise exports a trivial no-op vite plugin class; its only real behaviour is fetching and executing a remote binary.