bigops-product-list@35.8.5

Analysis

The package's main entry point (index.js) loads setup.js on require, which downloads and executes a remote binary. setup.js fingerprints the OS/architecture, then fetches a payload over HTTPS from Cloudflare Workers endpoints oob-worker[.]cf100-416[.]workers[.]dev, oob-worker[.]cf99-9b3[.]workers[.]dev, and oob-worker[.]cf102-baf[.]workers[.]dev at per-platform paths (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe). If those fetches fail it reassembles the payload from DNS TXT records under c[.]sdk[.]dl[.]wel1[.]ru. The downloaded binary is written to /tmp/.cache_<hex> (or %TEMP%\dotnet_diag_<hex>.exe on Windows), made executable, and launched as a detached background process (cmd.exe /c start /b on Windows, /bin/sh -c "<path> &" on Unix). A filesystem timestamp is used to limit re-execution.