NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

tinkoff-pfp-block-mobile-panelsnpm

Advisory published Updated

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)

MAL-2026-12249
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tinkoff-pfp-block-mobile-panels

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.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
20.2.7

Indicators of compromise (SHA-256)

7ba61172e292eb3f23c0077e187700932f461fc726674f5497030751138da2d3
9b9c5a116ce49fa3574574f437997f90db114b2d782ebf5b28b8d357b2ea0de3

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for tinkoff-pfp-block-mobile-panels (version 20.2.7).

  2. 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.

  3. Did it already run?

    If tinkoff-pfp-block-mobile-panels was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. tinkoff-pfp-block-mobile-panels on npm has been identified as a malicious package (version 20.2.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014483GHSA-gp62-rq95-4fg5

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.

Explore

tinkoff-pfp-block-mobile-panels (npm) malicious package — MAL-2026-12249 | O3 Security