tinkoff-statist-browser-typed-client-sme.platform.mobile.dynamicteasers.commonnpm
tinkoff-statist-browser-typed-client-sme.platform.mobile.dynamicteasers.common is a confirmed malicious npm package (MAL-2026-12270) that executes malicious code on install (malicious version 20.8.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-sme.platform.mobile.dynamicteasers.common (npm)
What this malware does
On require/import, index.js loads bridge.js which selects a platform-specific endpoint and downloads an opaque executable over HTTPS from hardcoded hosts assembled via string-join obfuscation (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT chunked base64 fallback via *.dl.well1.site. The downloaded bytes are written to disguised paths (/var/tmp/.cache<hex> on Unix, %TEMP%\dotnet_diag_<hex>.exe on Windows), chmod'd 0o755, and spawned detached via /bin/sh -c or cmd /c start /b. Hostnames are reconstructed from character-fragment arrays via.join(), staging filenames masquerade as system diagnostics/cache artifacts, and DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env checks are used as cover. The package name presents as a scoped Tinkoff internal client but the shipped code performs full remote code execution on the installer's host at load time.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind 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.dynamicteasers.common (version 20.8.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-sme.platform.mobile.dynamicteasers.common across your stack and pipelines.
If you installed it — respond
Remove tinkoff-statist-browser-typed-client-sme.platform.mobile.dynamicteasers.common from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tinkoff-statist-browser-typed-client-sme.platform.mobile.dynamicteasers.common 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.dynamicteasers.common 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.dynamicteasers.common-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.