tinkoff-statist-browser-typed-client-mb.product.tgeofencingnpm
tinkoff-statist-browser-typed-client-mb.product.tgeofencing is a confirmed malicious npm package (MAL-2026-12268) that typosquats a legitimate package to trick installs (malicious version 20.9.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-mb.product.tgeofencing (npm)
What this malware does
On require() of this package, index.js loads platform.js which assembles remote hostnames at runtime by concatenating fragmented string arrays to hide them from static scanners. The resolved hosts include oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, and tin/tina/ldr/win.dl.well1.site, with a DNS-TXT chunked base64 fallback channel. The module downloads an opaque binary via https.get, writes it to /tmp or %TEMP% under disguised names impersonating.NET diagnostics (dotnet_diag<hex>.exe,.cache_<hex>), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A sibling file lib/telemetry.js ships the same dropper shape (child_process require string-split as require("child_"+"process"), chmodSync via fs["chmod"+"Sync"], cp.spawn("/bin/sh", ["-c", filePath+" &"])) as a staged secondary payload, though it is not reached from index.js in this version. The fetched-and-executed binaries, obfuscated destinations, disguised filenames, and DNS-TXT fallback do not match the package's declared Tgeofencing purpose. The package name also impersonates a Tinkoff internal-scope package, consistent with a dependency-confusion lure.
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-mb.product.tgeofencing (version 20.9.6). 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-mb.product.tgeofencing across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-mb.product.tgeofencing is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-mb.product.tgeofencing, 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-mb.product.tgeofencing 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-mb.product.tgeofencing 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-mb.product.tgeofencing-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.