tinkoff-statist-browser-typed-client-sme.rko.authorization.commonnpm
tinkoff-statist-browser-typed-client-sme.rko.authorization.common is a confirmed malicious npm package (MAL-2026-12273) that typosquats a legitimate package to trick installs (malicious version 20.5.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-sme.rko.authorization.common (npm)
What this malware does
The package typosquats an internal Tinkoff scope name. On require(), index.js loads init.js, which builds attacker hostnames at runtime from string-fragment arrays joined via.join("") (e.g., ["oob-wor","ker.cf100","-416.wor","kers",".dev"].join("")), downloads an opaque binary from one of four Cloudflare Workers mirrors (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev) with DNS TXT fallback via tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site, writes it to /tmp or %TEMP% under names mimicking Microsoft diagnostics (dotnet_diag<hex>.exe /.cache_<hex>), applies executable permissions via fs["chmod"+"Sync"], and spawns it detached via cp.spawn("/bin/sh", ["-c", filePath + " &"], {detached:true}) or cmd.exe. Dangerous APIs are split-string-obfuscated (require("child_"+"process"), os["host"+"name"]) to evade string scanners. lib/telemetry.js contains a redundant WorkerHost download-and-execute path with base64 payload decoding and the same spawn/chmod primitives. An opt-out env-var check (DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK) and a /tmp/.analytics_state stamp gate limit re-execution to roughly once per six hours, characteristic of dropper anti-analysis rather than legitimate telemetry. The declared "shared primitives" purpose is inconsistent with fetching and executing a native binary.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind 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.rko.authorization.common (version 20.5.5). 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.rko.authorization.common across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-sme.rko.authorization.common is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-sme.rko.authorization.common, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If tinkoff-statist-browser-typed-client-sme.rko.authorization.common 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.rko.authorization.common 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.rko.authorization.common-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.