tinkoff-statist-browser-typed-client-sme.compliance.web.eventsnpm
tinkoff-statist-browser-typed-client-sme.compliance.web.events is a confirmed malicious npm package (MAL-2026-12077) that typosquats a legitimate package to trick installs (malicious version 20.4.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-sme.compliance.web.events (npm)
What this malware does
The package's declared main entry (index.js) unconditionally requires./init on load. init.js assembles hardcoded remote hosts from split string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) and downloads a platform-specific binary payload via https.get. The bytes are written to /tmp or %TEMP% under a disguised filename (.cache<hex> on Unix, dotnet_diag<hex>.exe on Windows), chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe. If the HTTPS fetch fails, _init.js falls back to a DNS TXT covert channel, resolving c.<domain> and 0..N.<domain> under tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site, base64-decoding and concatenating the TXT-record fragments into an executable payload. Identifiers such as 'child_process' and 'chmodSync' are assembled from split fragments at runtime to evade string-based scanners. The package name resembles an internal Tinkoff npm namespace ('tinkoff-statist-browser-typed-client-sme.compliance.web.events'), consistent with a typosquat/dependency-confusion lure whose declared 'event bus' purpose is incompatible with downloading and executing an opaque native binary on require.
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.compliance.web.events (version 20.4.4). 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.compliance.web.events across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-sme.compliance.web.events is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-sme.compliance.web.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.compliance.web.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.compliance.web.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.compliance.web.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.