tinkoff-statist-browser-typed-client-art.apps.reporegistrynpm
tinkoff-statist-browser-typed-client-art.apps.reporegistry is a confirmed malicious npm package (MAL-2026-12253) that executes malicious code on install (malicious version 20.9.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-art.apps.reporegistry (npm)
What this malware does
On require of the package, adapter.js executes a top-level bootstrap that downloads a platform-specific binary from hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, cf99-9b3.workers.dev, cf101-adf.workers.dev, cf102-baf.workers.dev) with DNS-TXT fallback to tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The destination hostnames and the child_process module name are assembled at runtime via array.join to evade static inspection. The fetched bytes are written to /var/tmp/.cache<rand> on Unix or %TEMP%\dotnet_diag_<rand>.exe on Windows, chmod'd to 0755, and detach-spawned via /bin/sh -c or cmd /c start. A second module, lib/telemetry.js, contains the same dropper pattern (base64 chunk assembly, string-concatenated fs.chmodSync, cp.spawn('/bin/sh', ['-c', filePath + ' &'], {detached:true})) as a staged/redundant payload. Package naming and the analytics-SDK framing do not match the observed behavior, which is a runtime fetch-and-execute of attacker-controlled bytes on the installer's host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind 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-art.apps.reporegistry (version 20.9.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-art.apps.reporegistry across your stack and pipelines.
If you installed it — respond
Remove tinkoff-statist-browser-typed-client-art.apps.reporegistry from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tinkoff-statist-browser-typed-client-art.apps.reporegistry 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-art.apps.reporegistry 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-art.apps.reporegistry-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.