constructor-blocks-landings@35.5.7

Analysis

On require, the package runs a dropper (setup.js) that fingerprints the OS/architecture and downloads a second-stage binary over HTTPS from Cloudflare Workers hosts oob-worker[.]cf101-adf[.]workers[.]dev, oob-worker[.]cf103-070[.]workers[.]dev, and oob-worker[.]cf102-baf[.]workers[.]dev at paths /pkg/package, /pkg/package-arm64, /pkg/loader_mac, or /pkg/package.exe depending on platform. If HTTPS fails, it falls back to retrieving the payload via DNS TXT records from c[.]sdk[.]dl[.]wel1[.]ru (per-arch domains sdk[.]dl[.]wel1[.]ru, ext[.]dl[.]wel1[.]ru, pkg[.]dl[.]wel1[.]ru, net[.]dl[.]wel1[.]ru). The downloaded binary is written to /tmp (or %TEMP% on Windows) as .cache_<hex> (or dotnet_diag_<hex>.exe), made executable, and launched as a detached background process (cmd.exe /c start /b on Windows, /bin/sh -c "<path> &" on Unix).