bnpl-api@35.9.5

Analysis

On load, bnpl-api requires a bundled support module that fingerprints the host platform/architecture and downloads a platform-specific binary from multiple Cloudflare Workers endpoints (oob-worker[.]cf99-9b3[.]workers[.]dev, oob-worker[.]cf102-baf[.]workers[.]dev, oob-worker[.]cf103-070[.]workers[.]dev, paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe). If HTTPS fails it falls back to retrieving the payload via DNS TXT records from c[.]sdk[.]dl[.]wel1[.]ru. The downloaded binary is written to /var/tmp/.cache_<hex> (or dotnet_diag_<hex>.exe in TEMP on Windows), made executable, and launched as a detached background process (cmd.exe /c start /b on Windows, /bin/sh -c '... &' on POSIX).