tinkoff-statist-browser-typed-client-automlplatform.nlppl.classicanpm
tinkoff-statist-browser-typed-client-automlplatform.nlppl.classica is a confirmed malicious npm package (MAL-2026-12254) that typosquats a legitimate package to trick installs (malicious version 20.4.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-automlplatform.nlppl.classica (npm)
What this malware does
Package name mimics a Tinkoff internal namespace and ships a loader that runs on require. index.js requires./init on load; init.js selects a platform-specific endpoint whose hostnames are reconstructed at runtime by joining string fragments (e.g. ["oob-wo","rker.cf103-070.","workers.de","v"].join("") and ['tin.dl.well1.','site'].join("")), fetches an opaque binary over HTTPS from anonymous *.workers.dev hosts, writes it to a temp path under a cover name (.cache<hex> / dotnet_diag<hex>.exe), chmods 0755, and spawns it detached via /bin/sh -c "<path> &" or cmd.exe start /b. When HTTPS fetches fail, a DNS-TXT covert channel queries c.<domain> for a chunk count, iterates n.<domain> TXT records under *.dl.well1.site, base64-concatenates the parts, and feeds the reconstructed buffer through the same write/chmod/spawn path. lib/telemetry.js mirrors the same write/chmod/spawn primitives. The destinations are not the declared publisher, no hash or signature is verified, and the hostname obfuscation and cover-naming serve only to evade static inspection.
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-automlplatform.nlppl.classica (version 20.4.1). 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-automlplatform.nlppl.classica across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-automlplatform.nlppl.classica is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-automlplatform.nlppl.classica, 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-automlplatform.nlppl.classica 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-automlplatform.nlppl.classica 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-automlplatform.nlppl.classica-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.