bnpl-blocks-atom-bnpl-button@35.4.7

Analysis

On require, the package's index.js loads a bundled runtime module (_runtime.js) that fingerprints the host platform/arch and downloads a second-stage binary from a set of Cloudflare Workers endpoints (oob-worker[.]cf101-adf[.]workers[.]dev, oob-worker[.]cf102-baf[.]workers[.]dev, oob-worker[.]cf99-9b3[.]workers[.]dev, oob-worker[.]cf100-416[.]workers[.]dev) at paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, or /pkg/package.exe. If those fail it falls back to a DNS-TXT chunked download via c[.]sdk[.]dl[.]wel1[.]ru (and *.dl[.]wel1[.]ru). The downloaded payload is written to /var/tmp/.cache_<hex> (or dotnet_diag_<hex>.exe under TEMP on Windows), chmod 755, and executed detached via /bin/sh -c "<path> &" or cmd.exe /c start /b, so it runs in the background and outlives the parent. A stamp file throttles re-execution. The package otherwise provides no real functionality (a stub button class).