CRITICAL npm Malware

Malicious code in tinkoff-statist-browser-typed-client-mb.reliability.android.events (npm)

MAL-2026-12269 · GHSA-4rph-fx37-hfvw

Published · Modified

Dependency scanning

Check whether tinkoff-statist-browser-typed-client-mb.reliability.android.events is in your codebase

Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.

Description


__

Source: amazon-inspector (10c12f5330c144cfe67198d49d442d702f5e40977e1d607ab651d33dffb2d073)

index.js unconditionally requires./loader on module load. loader.js selects a platform-specific payload path for Linux/macOS/Windows, downloads a binary over HTTPS from a rotating list of Cloudflare Workers subdomains (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 chunked base64 fallback resolving via tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site. The fetched bytes are written to /tmp or %TEMP% under a disguised name (dotnet_diag.exe or.cache), chmod 0755 on POSIX, and spawned detached via cp.spawn("/bin/sh", ["-c", path + " &"]).unref(). No hash or signature verification is performed. Host destinations are reconstructed at runtime via.join("") on split string fragments to evade static analysis. A sibling module lib/telemetry.js contains identical dropper primitives with additional bracketed-property obfuscation (fs["chmod"+"Sync"], require("child_"+"process")). The package name resembles an internal Tinkoff analytics client but the network destinations, payload naming, and obfuscation shape have no relation to the declared purpose.

Source: ghsa-malware (e71f757940749e130afe4ec6444feb19a188d16f1257e8ca9869ff995197a159)

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.

Ready to move

Start Securing

Free, no credit card | First findings in minutes