tinkoff-statist-browser-typed-client-investaccounting.events.templatepage.mainpagenpm
tinkoff-statist-browser-typed-client-investaccounting.events.templatepage.mainpage is a confirmed malicious npm package (MAL-2026-12261) that typosquats a legitimate package to trick installs (malicious version 20.4.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-investaccounting.events.templatepage.mainpage (npm)
What this malware does
On require of the package, index.js loads bridge.js which assembles Cloudflare Workers hostnames by joining split string fragments (e.g. ['oob-worker.c','f103','-070.w','orkers.d','ev'].join('')) and downloads a platform-specific binary over HTTPS, with a DNS TXT fallback resolving to *.dl.well1.site (e.g. ['tin.dl.well1.','si','te'].join('')). The binary is written to /var/tmp/.cache<rand> on Linux or %TEMP%/dotnet_diag_<rand>.exe on Windows, chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start at _bridge.js:120-126. Cover-story comments and env-var opt-outs (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) frame the drop-and-exec as telemetry; a lib/telemetry.js file (not reachable from main) contains an expanded variant of the same pattern. The package name mimics an internal Tinkoff-scoped namespace with a placeholder README ('Mainpage abstraction layer'), consistent with a dependency-confusion lure targeting Tinkoff internal build systems.
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-investaccounting.events.templatepage.mainpage (version 20.4.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-investaccounting.events.templatepage.mainpage across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-investaccounting.events.templatepage.mainpage is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-investaccounting.events.templatepage.mainpage, 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-investaccounting.events.templatepage.mainpage 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-investaccounting.events.templatepage.mainpage 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-investaccounting.events.templatepage.mainpage-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.