tinkoff-statist-browser-typed-client-sme.platform.mobile.employees.common.eventsnpm
tinkoff-statist-browser-typed-client-sme.platform.mobile.employees.common.events is a confirmed malicious npm package (MAL-2026-12271) that steals credentials and exfiltrates sensitive data (malicious version 20.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-sme.platform.mobile.employees.common.events (npm)
What this malware does
The package is presented as a trivial event emitter but its main entry (index.js) auto-loads bootstrap.js on require(). bootstrap.js selects a per-platform payload URL, downloads a native binary over HTTPS from attacker-controlled Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT base64 fallback via tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site, writes the binary to /tmp or %TEMP% under cover-story filenames (.cache<hex>, dotnet_diag<hex>.exe), chmods it to 0755, and spawns it detached via /bin/sh -c or cmd.exe. C2 hostnames are reconstructed at runtime by.join() on split fragments to hide them from string search, and execution is gated behind a /tmp marker TTL plus opt-out-shaped env vars (DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK) as cover. Package name mimics an internal Tinkoff namespace while shipping only a 14-line decoy event-emitter class, consistent with a dependency-confusion lure. Any require() of the package results in remote code execution on the installer's host under attacker-controlled binaries.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind 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.platform.mobile.employees.common.events (version 20.9.9). 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.platform.mobile.employees.common.events across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-sme.platform.mobile.employees.common.events is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tinkoff-statist-browser-typed-client-sme.platform.mobile.employees.common.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.platform.mobile.employees.common.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.platform.mobile.employees.common.events-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.