twork-data-services-customer-api-v2-customer-vip-status @20.9.7

Summary

On require of this package, index.js loads _platform.js which selects a platform-specific payload (linux_x64/linux_arm64/darwin/win32), downloads an opaque binary over HTTPS from a pool of *.workers.dev hosts, writes it to /var/tmp/.cache_<hex> or %TEMP%/dotnet_diag_<hex>.exe, chmods it 0755, and spawns it detached via /bin/sh or cmd with unref, so execution survives the parent process. Destination hostnames are not stored as plain literals — they are assembled at runtime from split fragments (e.g. ['oob-worker.cf101-a','df.worke','rs.d','ev'].join('')) to evade string scans. If HTTPS retrieval fails, the code falls back to DNS TXT lookups against numbered subdomains of dl.well1.site and reassembles a base64-encoded binary from the concatenated TXT records, bypassing HTTPS egress inspection. The disguised on-disk filenames (dotnet_diag_*,.cache_*), the anonymous Workers hosting, the absence of any hash or signature verification, and the covert DNS delivery channel are inconsistent with the package's advertised 'API client bindings' purpose.

Source: amazon-inspector (bd6182daf75450f1e553f81c3979a275c481690e27d04712285b85a25ebadc3b)