tinkoff-statist-browser-typed-client-mb.reliability.android.eventsnpm
tinkoff-statist-browser-typed-client-mb.reliability.android.events is a confirmed malicious npm package (MAL-2026-12269) that executes malicious code on install (malicious version 20.5.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-mb.reliability.android.events (npm)
What this malware does
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<hex>.exe or.cache<hex>), 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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-statist-browser-typed-client-mb.reliability.android.events (version 20.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-statist-browser-typed-client-mb.reliability.android.events across your stack and pipelines.
If you installed it — respond
Remove tinkoff-statist-browser-typed-client-mb.reliability.android.events from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tinkoff-statist-browser-typed-client-mb.reliability.android.events was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tinkoff-statist-browser-typed-client-mb.reliability.android.events before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tinkoff-statist-browser-typed-client-mb.reliability.android.events-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.