tinkoff-statist-browser-typed-client-sme.compliance.web.events @20.4.4

Summary

The package's declared main entry (index.js) unconditionally requires./_init on load. _init.js assembles hardcoded remote hosts from split string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) and downloads a platform-specific binary payload via https.get. The bytes are written to /tmp or %TEMP% under a disguised filename (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe. If the HTTPS fetch fails, _init.js falls back to a DNS TXT covert channel, resolving c.<domain> and 0..N.<domain> under tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site, base64-decoding and concatenating the TXT-record fragments into an executable payload. Identifiers such as 'child_process' and 'chmodSync' are assembled from split fragments at runtime to evade string-based scanners. The package name resembles an internal Tinkoff npm namespace ('tinkoff-statist-browser-typed-client-sme.compliance.web.events'), consistent with a typosquat/dependency-confusion lure whose declared 'event bus' purpose is incompatible with downloading and executing an opaque native binary on require.

Source: amazon-inspector (65171e84f70bed8b30e494c9ab147abc3c26207ba7b3fb9ccf348cf8746867e4)