dolyame-boxy-atom-bnpl-button (npm) · Malicious Code

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (963f070cd6563a11008f0726b4e0a11e5612dce9b53c58d9ea537566ab1774e2) On require, index.js loads _helpers.js which fetches a platform-specific binary from obfuscated hosts assembled via array-join (oob-worker.cf*.workers.dev) with a DNS-TXT chunked-base64 fallback channel to *.dl.wel1.ru, writes the bytes to /tmp/.cache_<rnd> or %TEMP%/dotnet_diag_<rnd>.exe, chmods 0755, and spawns the file detached via cp.spawn('/bin/sh',['-c', fp+' &'],{detached:true}) or cmd equivalent on Windows. No integrity or signature check is performed on the fetched bytes. Destination hostnames are string-split to evade static detection, and file/lock names (analytics_state, dotnet_diag_*.exe,.cache_*) plus code comments framing the spawn as 'Detached process to avoid blocking npm install' present the behavior as telemetry. A lockfile with a ~22000s max age throttles re-fetching into a scheduled beacon pattern. The DNS-TXT channel provides a covert payload path when HTTPS egress is blocked. Any installer requiring this package executes attacker-controlled arbitrary code on their host. ## Source: ghsa-malware (4fcffe6de0ccd3c2c780baeec4bc4617727847bcd6170d0bd92d067abc3fade4) 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.

• npmjs.com/package/dolyame-boxy-atom-bnpl-button/v/35.8.3 (opens in a new tab)
• github.com/advisories/GHSA-xp3x-7m7p-57w6 (opens in a new tab)