devplatform-spa-plugin-history@35.1.4

Analysis

On load, the package downloads and executes a second-stage binary. It fingerprints the platform/arch, then fetches a payload over HTTPS from oob-worker[.]cf101-adf[.]workers[.]dev/pkg/package, oob-worker[.]cf102-baf[.]workers[.]dev/pkg/package, or oob-worker[.]cf100-416[.]workers[.]dev/pkg/package (rotated randomly); if those fail it reassembles a base64 payload from DNS TXT records on sdk[.]dl[.]wel1[.]ru, ext[.]dl[.]wel1[.]ru, pkg[.]dl[.]wel1[.]ru, or net[.]dl[.]wel1[.]ru. The downloaded binary is written to /var/tmp/.cache_<hex> (or dotnet_diag_<hex>.exe in the temp dir on Windows), made executable, and launched detached via /bin/sh -c or cmd.exe /c start /b. A marker file /tmp/.analytics_state throttles re-execution for ~6 hours.