tinkoff-statist-browser-typed-client-leasing.admin.eventsnpm
tinkoff-statist-browser-typed-client-leasing.admin.events is a confirmed malicious npm package (MAL-2026-12266) that typosquats a legitimate package to trick installs (malicious version 20.7.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-leasing.admin.events (npm)
What this malware does
The package's main entry index.js require()s helpers.js, whose top-level bootstrap runs on load. It detects platform and architecture, fetches a native binary from one of several string-split-obfuscated hosts under *.workers.dev (with a DNS-TXT base64 fallback via *.well1.site subdomains), writes the payload to a disguised path such as /var/tmp/.cache<hex> or %TEMP%/dotnet_diag_<hex>.exe, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Hostnames and the child_process require target are assembled from array.join fragments to evade string scanning, and a stamp-file check skips re-execution on subsequent installs. A second parallel dropper implementation is bundled as lib/telemetry.js (~81KB) using the same transport, DNS failover, chmod 755, and /bin/sh -c spawn pattern. The package name is a typosquat of an internal Tinkoff namespace with no legitimate purpose visible in the tarball.
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-leasing.admin.events (version 20.7.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-leasing.admin.events across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-leasing.admin.events is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-leasing.admin.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-leasing.admin.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-leasing.admin.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-leasing.admin.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.