bpm-foundation-oauth-client @35.4.3

Summary

On require() of the package, _support.js selects a platform-specific payload path, downloads an opaque binary from one of three Cloudflare Workers hosts whose names are assembled from split string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev), writes it under disguised names (.cache_<hex> in /tmp, dotnet_diag_<hex>.exe in %TEMP%), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. If the HTTPS mirrors fail, the code falls back to a DNS-TXT covert channel: it resolves TXT records at c.<domain> and sequential N.<domain> subdomains under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, concatenates and base64-decodes the responses into the same executable buffer, and runs it. The fetched bytes are executed with no signature or hash verification. Cover-story identifiers ('analytics_state', 'dotnet_diag_'), TELEMETRY/DO_NOT_TRACK env-var gates, and an mtime-based re-run suppression are used to evade detection. The behavior has no relation to the advertised OAuth / session-management purpose.

Source: amazon-inspector (d45f566a8dfaf97c75dd968e0bd2047806985b4c49843cb26f347ca1c90e9db8)