tinkoff-statist-browser-typed-client-sme.users.origination.webnpm
tinkoff-statist-browser-typed-client-sme.users.origination.web is a confirmed malicious npm package (MAL-2026-12277) that executes malicious code on install (malicious version 20.6.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-sme.users.origination.web (npm)
What this malware does
The package's main entry require()'s loader.js, which at import time downloads a per-platform binary from string-concatenation-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS-TXT chunk-reassembly fallback over subdomains of dl.well1.site. The fetched bytes are written to a disguised path under /var/tmp or %TEMP% (e.g..cache<hex> or dotnet_diag_<hex>.exe), chmod'd to 0755 via bracketed property access (fs["chmod"+"Sync"]), and executed detached via cp.spawn("/bin/sh", ["-c", path + " &"]) or cp.spawn("cmd.exe", ["/c", "start", "/b", path]). API names and hostnames are hidden behind array-join concatenation (require("child_"+"process"), ["oob-worker",".cf103-070.w","orkers.dev"].join("")) to evade static detection. A second copy of the dropper is shipped in lib/telemetry.js under an "Analytics SDK" cover story, using the same primitives (base64-chunk Buffer assembly, disk write, chmod 0755, /bin/sh spawn). The fetched payload is opaque, unpinned, unverified, and delivered from non-publisher-controlled infrastructure with a covert DNS channel; the destinations do not match the package's declared scope (a Tinkoff-branded internal typed client).
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.
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.users.origination.web (version 20.6.2). 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.users.origination.web across your stack and pipelines.
If you installed it — respond
Remove tinkoff-statist-browser-typed-client-sme.users.origination.web 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.users.origination.web 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.users.origination.web 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.users.origination.web-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.