tinkoff-pfp-block-mobile-panelsnpm
tinkoff-pfp-block-mobile-panels is a confirmed malicious npm package (MAL-2026-12249) that typosquats a legitimate package to trick installs (malicious version 20.2.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-pfp-block-mobile-panels (npm)
What this malware does
On require() of the package, helpers.js selects a platform-specific binary path, downloads bytes from one of four hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev) with DNS-based fallback via subdomains of well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site), writes the payload to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe. Host names and dangerous API names (child_process, chmodSync) are assembled at runtime from split strings via.join('') to evade static analysis. index.js unconditionally require('./_helpers'), so the dropper fires on any import of the package. A second dropper variant with the same shape ships in lib/telemetry.js (~81KB, currently unreferenced from index.js). Package name impersonates the Tinkoff brand and README references an 'internal tracker' to suggest insider legitimacy, consistent with a dependency-confusion lure targeting Tinkoff-adjacent developer workstations.
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-pfp-block-mobile-panels (version 20.2.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-pfp-block-mobile-panels across your stack and pipelines.
If you installed it — respond
tinkoff-pfp-block-mobile-panels is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-pfp-block-mobile-panels, 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-pfp-block-mobile-panels 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-pfp-block-mobile-panels 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-pfp-block-mobile-panels-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.