bnpl-blocks-atom-bnpl-dangerously-html@35.2.4

Analysis

On require, the package downloads and executes a second-stage binary. It fetches a platform-specific payload over HTTPS from Cloudflare Workers endpoints oob-worker[.]cf102-baf[.]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 depending on OS/arch. If those fail, it falls back to a DNS-TXT channel that reassembles the payload from base64 TXT records under the domain c[.]sdk[.]dl[.]wel1[.]ru. The downloaded binary is written to /var/tmp/.cache_<hex> (or dotnet_diag_<hex>.exe under 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 also writes a state marker file to /tmp/.analytics_state to rate-limit re-execution.