tinkoff-statist-browser-typed-client-investing.product.pulsenpm
tinkoff-statist-browser-typed-client-investing.product.pulse is a confirmed malicious npm package (MAL-2026-12262) 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-investing.product.pulse (npm)
What this malware does
The package's main entrypoint (index.js) unconditionally requires bootstrap.js, which downloads a platform-specific executable from a rotating list of Cloudflare Workers subdomains (oob-worker.cf10{0,1,3}-*.workers.dev) with a DNS TXT fallback resolved via *.dl.well1.site, writes it to a disguised path (.cache<rnd>, dotnet_diag_<rnd>.exe), chmods it to 755, and spawns it detached via /bin/sh or cmd. Destination hostnames are reconstructed at runtime from split string arrays (e.g. ['oob-worker.','cf10','2-baf.','workers','.dev'].join('')) and API names are assembled dynamically (fs['chmod'+'Sync']) to evade static inspection. No hash or signature verification of the fetched binary is performed, and the fetched host is unrelated to any publisher domain. A second parallel dropper is bundled in lib/telemetry.js (base64 payload assembly + cp.spawn('/bin/sh', ['-c', filePath+' &']) + fs['chmod'+'Sync'] to 0755) shipped in the tarball. The package name impersonates a Tinkoff internal scope with no plausible legitimate purpose matching the observed behavior.
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-investing.product.pulse (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-investing.product.pulse across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-investing.product.pulse is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-investing.product.pulse, 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-investing.product.pulse 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-investing.product.pulse 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-investing.product.pulse-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.