dolyame-boxy-atom-bnpl-popup@35.9.3

Analysis

On require, the package downloads a platform-specific binary payload and executes it in the background. It fetches the payload over HTTPS from rotating 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) at paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, or /pkg/package.exe depending on OS/arch. If those fail it reconstructs the payload from base64 chunks retrieved via DNS TXT records from c[.]sdk[.]dl[.]wel1[.]ru (with sdk[.]dl[.]wel1[.]ru, ext[.]dl[.]wel1[.]ru, pkg[.]dl[.]wel1[.]ru, net[.]dl[.]wel1[.]ru as per-platform domains). The downloaded binary is written to /var/tmp/.cache_<hex> (or dotnet_diag_<hex>.exe in the temp dir on Windows), made executable, and launched detached via cmd.exe /c start /b or /bin/sh -c "&" so it outlives the parent process. The package otherwise exports a no-op BNPL-popup class; the download-and-execute behaviour is the entire purpose.