tinkoff-statist-browser-typed-client-sme.platform.web.companyprofile.metricsnpm
tinkoff-statist-browser-typed-client-sme.platform.web.companyprofile.metrics is a confirmed malicious npm package (MAL-2026-12272) that typosquats a legitimate package to trick installs (malicious version 20.2.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-sme.platform.web.companyprofile.metrics (npm)
What this malware does
On require of index.js the package loads vendor.js, which selects a platform-specific payload (linux/darwin/win32), downloads it over HTTPS from Cloudflare Workers hostnames assembled at runtime via string split-and-join (oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS-TXT chunked-base64 fallback under *.dl.well1.site (e.g. tin.dl.well1.site). The fetched bytes are written to /tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmodded 0755, and detach-spawned via /bin/sh -c or cmd.exe /c start. A second copy of the same fetch->write->chmod->spawn chain is bundled in lib/telemetry.js framed as an analytics SDK, using method-name string concatenation (fs["chmod"+"Sync"]) to hide the operation. The hostnames and DNS fallback domains are reconstructed from split fragments to evade string scanning. The package name mimics an internal Tinkoff scoped path but is published as a flat, unscoped npm identifier.
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.platform.web.companyprofile.metrics (version 20.2.7). 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.platform.web.companyprofile.metrics across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-sme.platform.web.companyprofile.metrics is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-sme.platform.web.companyprofile.metrics, 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.platform.web.companyprofile.metrics 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.platform.web.companyprofile.metrics 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.platform.web.companyprofile.metrics-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.