bigops-watchdog-angular @35.4.8

Summary

On require() of the package, index.js loads _vendor.js which selects a platform-specific URL, downloads an opaque binary from one of several Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback channel over sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache_<hex> or %TEMP%\dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via /bin/sh -c or cmd. Endpoint hostnames are split into fragments and reassembled at runtime via Array.join('') to evade static scanners. No hash or signature verification is performed, the destinations are hardcoded and unrelated to any stated Angular/watchdog purpose, and the staged binaries use disguised cache/diagnostic filenames. The result is arbitrary attacker-controlled code execution on any machine that installs or imports the package.

Source: amazon-inspector (d7bfa2b0d9464df6662fddb4e969b42ef35465f2c70ba39943ac3fb0265aa781)