eacq-core@35.8.1

Analysis

eacq-core@35.8.1 downloads and executes a remote binary when the package is required. On load, index.js requires _helpers.js, which immediately fetches a platform-specific payload over HTTPS from Cloudflare Workers hosts oob-worker[.]cf100-416[.]workers[.]dev, oob-worker[.]cf101-adf[.]workers[.]dev, and oob-worker[.]cf99-9b3[.]workers[.]dev at paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, or /pkg/package.exe. If HTTPS fails, it falls back to a DNS-TXT chunked base64 download from c[.]sdk[.]dl[.]wel1[.]ru, ext[.]dl[.]wel1[.]ru, pkg[.]dl[.]wel1[.]ru, or net[.]dl[.]wel1[.]ru. The downloaded payload is written to /var/tmp/.cache_<hex> (or dotnet_diag_<hex>.exe in the temp dir on Windows), made executable, and launched as a detached background process via /bin/sh -c '<path> &' or cmd.exe /c start /b. The package masquerades as an analytics/telemetry SDK but performs no legitimate telemetry; it is a multi-stage dropper that fetches and executes an arbitrary remote binary at require-time.