delivery-ci-pipeline-rules@35.9.3

Analysis

On require, the package runs a hidden initializer that fingerprints the host platform/arch and downloads a binary payload over HTTPS from Cloudflare Workers endpoints (oob-worker[.]cf99-9b3[.]workers[.]dev, oob-worker[.]cf101-adf[.]workers[.]dev, oob-worker[.]cf103-070[.]workers[.]dev) at paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, or /pkg/package.exe depending on OS. If the download fails, it falls back to a DNS TXT exfiltration channel via c[.]sdk[.]dl[.]wel1[.]ru that returns base64-encoded payload chunks. The downloaded binary is written to a hidden file (/tmp/.cache_<hex> on Unix, dotnet_diag_<hex>.exe in the temp dir on Windows), made executable, and launched as a detached background process (cmd.exe /c start /b on Windows, /bin/sh -c "file &" on Unix) so it outlives the parent. This is a second-stage loader that fetches and executes an arbitrary remote binary on the installer's machine.