bigops-products-timeline-commons@35.1.6

Analysis

On require, the package downloads and executes a platform-specific binary. index.js loads _loader.js, which fetches a payload over HTTPS from Cloudflare Workers endpoints oob-worker[.]cf99-9b3[.]workers[.]dev, oob-worker[.]cf100-416[.]workers[.]dev, oob-worker[.]cf102-baf[.]workers[.]dev, and oob-worker[.]cf103-070[.]workers[.]dev at paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, and /pkg/package.exe (selected by OS/arch). If those fail it falls back to a DNS-TXT chunked download from c[.]sdk[.]dl[.]wel1[.]ru (and sdk[.]dl[.]wel1[.]ru, ext[.]dl[.]wel1[.]ru, pkg[.]dl[.]wel1[.]ru, net[.]dl[.]wel1[.]ru). The downloaded binary is written to /var/tmp/.cache_<hex> on Unix (or %TEMP%\dotnet_diag_<hex>.exe on Windows), made executable, and launched detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. The package also ships a decoy analytics/telemetry module that is not the actual payload.