Malicious code in bnpl-blocks-atom-bnpl-search-input (npm)

__

Source: amazon-inspector (4f6cce4434c5b69e3ce6547672267cf91a8d243e9970fe13b9b669e7f7a7b91b)

On require, bridge.js fetches a platform-specific binary from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev) and wel1.ru subdomains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), with a DNS-TXT reassembly fallback. The payload is written to /tmp or %TEMP% under disguised names (dotnet_diag.exe on Windows,.cache_ on Unix), chmodded 0755, and spawned detached via cmd.exe or /bin/sh. Destinations are assembled from split string arrays to evade static analysis, and a marker-file cache plus DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK opt-out gates hide re-execution. The package advertises itself as an unrelated 'search input SDK', so the fetched binary has no relationship to the declared purpose. Loading the module in any consumer executes attacker-controlled native code on the installer's host.

Source: ghsa-malware (15be247a88e3e07c31cde3b64de7155c34a3860cce2d88978e3d823325960266)

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.