Malicious code in tinkoff-statist-browser-typed-client-sme.compliance.web.events (npm)

__

Source: amazon-inspector (65171e84f70bed8b30e494c9ab147abc3c26207ba7b3fb9ccf348cf8746867e4)

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 on Unix, dotnet_diag.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. and 0..N. 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: ghsa-malware (213f5e3a5fc62959d609f9cdd0a82a5911271d45b2ae207d563537b693c40fe8)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.