devplatform-s3-client@35.9.5

Summary

On require of the package's main entry, _bridge.js assembles Cloudflare Workers hostnames from string fragments via Array.join (e.g. 'oob-worker.cf102-baf.workers.dev', 'cf101-adf.workers.dev', 'cf99-9b3.workers.dev'), downloads a platform-specific binary via https.get, writes it to /var/tmp or %TEMP% under a decoy name (.cache_<rnd> on Unix, dotnet_diag_<rnd>.exe on Windows), sets it executable with chmod 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. If HTTPS fetches fail, _bridge.js falls back to a DNS-TXT covert channel: it resolves TXT records at c.<domain> and numbered subdomains under an obfuscated 'sdk.dl.wel1.ru' family to reassemble a base64-encoded binary, then writes and executes it. A persistence-stamp file gates re-execution across imports. The hostnames are split into fragments to evade static grep, decoy filenames masquerade as OS diagnostic caches, and none of this behavior is part of an S3 client.

Source: amazon-inspector (618b016d2ee8f333f47ee78c4ffe29b703a08ab7fca524ee072944394fb1301c)