tinkoff-statist-browser-typed-client-sme.reporting.reportingnpm
tinkoff-statist-browser-typed-client-sme.reporting.reporting is a confirmed malicious npm package (MAL-2026-12050) 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-sme.reporting.reporting (npm)
What this malware does
On require() of the package, index.js loads vendor.js which selects a platform-specific endpoint and fetches a binary payload from one of four Cloudflare Workers hosts whose names are assembled at runtime via string split/join concatenation (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev), with DNS TXT-record fallback discovery via tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The fetched bytes are written to a randomized temp path with disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755 on POSIX, and executed detached via spawn("/bin/sh", ["-c", fp + " &"]) or spawn("cmd",...) on Windows. Hostnames and sensitive API names (child_process, chmodSync) are reconstructed from array joins to defeat static matching; a 22822-second cooldown flag suppresses re-execution. The package name imitates an internal Tinkoff scope while lib/telemetry.js is unused cover-story code. Installing or requiring this package executes attacker-controlled native code on the host.
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-sme.reporting.reporting (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-sme.reporting.reporting across your stack and pipelines.
If you installed it — respond
Remove tinkoff-statist-browser-typed-client-sme.reporting.reporting 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-sme.reporting.reporting 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-sme.reporting.reporting 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-sme.reporting.reporting-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.