bnpl-blocks-independent-bnpl-main-banner@35.4.4

Analysis

On require, the package fingerprints the platform/arch and downloads a second-stage binary over HTTPS from Cloudflare Workers hosts oob-worker[.]cf100-416[.]workers[.]dev, oob-worker[.]cf101-adf[.]workers[.]dev, and oob-worker[.]cf99-9b3[.]workers[.]dev (paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe). If those fail it falls back to a DNS TXT-based channel under sdk[.]dl[.]wel1[.]ru / ext[.]dl[.]wel1[.]ru / pkg[.]dl[.]wel1[.]ru / net[.]dl[.]wel1[.]ru. The downloaded payload is written to /tmp/.cache_<hex> (or dotnet_diag_<hex>.exe in TEMP on Windows) and executed detached via cmd.exe /c start /b on Windows or /bin/sh -c on Unix, so it runs in the background. The package's stated purpose (a UI banner component) is unrelated to this behaviour.