eacq-dialog@35.8.1

Analysis

eacq-dialog ships a loader (setup.js) that runs on require. It downloads a platform-specific binary from Cloudflare Workers endpoints (oob-worker[.]cf100-416[.]workers[.]dev, oob-worker[.]cf101-adf[.]workers[.]dev, oob-worker[.]cf102-baf[.]workers[.]dev, oob-worker[.]cf99-9b3[.]workers[.]dev, paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe). If HTTP fails it reconstructs the payload from DNS TXT records under c[.]sdk[.]dl[.]wel1[.]ru / c[.]ext[.]dl[.]wel1[.]ru / c[.]pkg[.]dl[.]wel1[.]ru / c[.]net[.]dl[.]wel1[.]ru. The downloaded binary is written to /var/tmp/.cache_<hex> (or %TEMP%\dotnet_diag_<hex>.exe on Windows), made executable, and launched as a detached background process via cmd.exe start /b or /bin/sh -c "&". The package executes this remote payload on install/require.