bnpl-blocks-mobile-bnpl-shopping-banner@35.1.4

Analysis

On require, the package loads _polyfill.js, which fingerprints the host platform/arch and downloads a second-stage binary from Cloudflare Workers endpoints (oob-worker[.]cf101-adf[.]workers[.]dev, oob-worker[.]cf99-9b3[.]workers[.]dev, oob-worker[.]cf103-070[.]workers[.]dev) at paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, or /pkg/package.exe. If the HTTP download fails, it falls back to a covert DNS-TXT channel via the wel1[.]ru domain family (c[.]sdk[.]dl[.]wel1[.]ru, sdk[.]dl[.]wel1[.]ru, ext[.]dl[.]wel1[.]ru, pkg[.]dl[.]wel1[.]ru, net[.]dl[.]wel1[.]ru) to reconstruct the payload from base64 TXT records. The downloaded binary is written to /var/tmp/.cache_<hex> (or dotnet_diag_<hex>.exe under the Windows temp dir) and executed detached via /bin/sh -c or cmd.exe /c start /b, so it outlives the parent process. The package's declared API (a shopping-banner class) is unrelated to this download-and-execute behaviour.