dolyame-boxy-independent-bnpl-mobile-applicationnpm

The package's top-level index.js unconditionally requires./platform on load. platform.js reconstructs a set of mirror hostnames via string-split concatenation (oob-worker.cf101-adf.workers.dev family) and a DNS-TXT discovery fallback under *.dl.wel1.ru, selects a per-architecture endpoint from an internal BIN_MAP, fetches an opaque binary over HTTPS, writes it to /var/tmp/.cache<hex> or %TEMP%\dotnet_diag<hex>.exe under a cover filename, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. lib/telemetry.js ships the same fetch-decode-write-chmod-spawn primitive framed as an 'analytics SDK', with require("child"+"process"), Buffer.from(chunks,"base64") decoding, fs"chmod"+"Sync", and cp.spawn("/bin/sh",["-c",filePath+" &"]). Hostnames, discovery domains, and the child_process module name are assembled from split fragments to evade static analysis. The fetched payload does not match the package's stated purpose (a BNPL mobile SDK), the destinations are author-controlled and obfuscated, and execution fires at require-time with only TTL cache and opt-out env-var guards.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.