tinkoff-statist-browser-typed-client-dss.insurance.servicenpm
tinkoff-statist-browser-typed-client-dss.insurance.service is a confirmed malicious npm package (MAL-2026-12257) that typosquats a legitimate package to trick installs (malicious version 20.3.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-dss.insurance.service (npm)
What this malware does
On require of the package, index.js loads runtime.js which fetches a platform-specific binary from anonymous Cloudflare Workers endpoints (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback to tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site, writes the payload to /tmp with a hidden dot-prefixed filename (or to the Windows temp directory as dotnet_diag<rand>.exe), chmods it to 0755, and detached-spawns it via /bin/sh -c or cmd. Destination hostnames and API names are reassembled from split string arrays (e.g. ["oob-worker.cf102-ba","f.work","ers.d","ev"].join(""), require("child_" + "process")) to evade static analysis. The tarball also ships lib/telemetry.js, an 81 KB secondary loader framed as a metrics SDK that contains the same drop-chmod-spawn primitives with base64-decoded chunks; it is not on the currently reachable import graph but duplicates the dropper capability. The package name impersonates a Tinkoff internal SDK; the anonymous Cloudflare Workers infrastructure and covert DNS fallback do not correspond to any first-party backend for the claimed purpose.
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-dss.insurance.service (version 20.3.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-dss.insurance.service across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-dss.insurance.service is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-dss.insurance.service, 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-dss.insurance.service 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-dss.insurance.service 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-dss.insurance.service-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.