Malicious code in tinkoff-component-infopanel (npm)

__

Source: amazon-inspector (1465530b7853077d8b3fb7896478a69f62f6506df775d2e959b3d9bae6861f11)

On require of the package, platform.js downloads a platform-specific native binary from hardcoded Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback resolved via *.dl.well1.site, writes the bytes to a masqueraded cache path (cover-story names such as dotnet_diag,.cache_,.analytics_state), chmods 0o755, and spawns it detached via /bin/sh -c or cmd. The destination hostnames are assembled at runtime by joining string fragments (e.g. ["oob-worker.cf10","0-416",".wo","rker","s.dev"].join("")) to evade static matching. No hash or signature verification is performed. The package name impersonates the Tinkoff brand while package.json declares an empty author, no repository, and a README labeling it an 'internal' module. The dropper fires via top-level require() from index.js, so importing this package as a dependency executes the fetched binary on the installer's host.

Source: ghsa-malware (6ed9672a3f7ff309e08f96ca257527dd752bab575c6e1d320efcc490773a3b2d)

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.