Malicious code in beaver-ui-pagination (npm)

__

Source: amazon-inspector (2db8f562892f21caf2a12230c52507a333a5ada223f98964094838657072adcb)

On require('beaver-ui-pagination'), index.js loads init.js which selects a platform key and downloads a binary from string-split-obfuscated hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS TXT chunked-base64 fallback via *.dl.wel1.ru subdomains. The fetched binary is written to /var/tmp or %TEMP% under a disguised name (.cache on POSIX, dotnet_diag_.exe on Windows), chmod 0755 on POSIX, and spawned detached via /bin/sh -c or cmd.exe. Destination hostnames are assembled at runtime from array.join to evade static inspection, and env-var opt-outs (DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK) plus an 'analytics_state' marker file frame the behavior as telemetry despite the fetch-and-execute flow. A sibling lib/telemetry.js not currently reachable from index.js ships a second copy of the dropper primitives (dynamic require('child_'+'process'), base64-chunked buffer, chmodSync 0755, /bin/sh spawn of a filePath).

Source: ghsa-malware (123cbe3def4ec949ca2a0fb1332af1a517ccd370290ba923f0f474a54761f4bf)

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.