tinkoff-statist-browser-typed-client-sme.rko.ta.ios.eventsnpm
tinkoff-statist-browser-typed-client-sme.rko.ta.ios.events is a confirmed malicious npm package (MAL-2026-12276) that typosquats a legitimate package to trick installs (malicious version 20.6.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-sme.rko.ta.ios.events (npm)
What this malware does
Package presents itself as a trivial event bus (index.js exports a small EventBus class) but its main entry unconditionally requires./ext on load. ext.js selects a platform-specific payload, downloads a binary from Cloudflare Workers hosts whose names are reassembled at runtime from split-string fragments (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS TXT fallback under tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site that base64-decodes chunked TXT records into a binary. The downloaded bytes are written to /tmp or %TEMP% under masqueraded names (dotnet_diag<rand>.exe,.cache<rand>), chmod 0755 on Unix, and spawned detached via cmd.exe or /bin/sh. Host strings and DNS discovery domains are concatenated from fragmented arrays to evade static analysis, and a no-op _l() function is scattered around the network I/O. The package name mimics an internal Tinkoff typed-client naming convention, consistent with a dependency-confusion attack against a private scope.
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-sme.rko.ta.ios.events (version 20.6.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-sme.rko.ta.ios.events across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-sme.rko.ta.ios.events is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-sme.rko.ta.ios.events, 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-sme.rko.ta.ios.events 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-sme.rko.ta.ios.events 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-sme.rko.ta.ios.events-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.