tinkoff-pfp-integration-mobile-slider-iconsnpm
tinkoff-pfp-integration-mobile-slider-icons is a confirmed malicious npm package (MAL-2026-12250) that steals credentials and exfiltrates sensitive data (malicious version 20.2.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-pfp-integration-mobile-slider-icons (npm)
What this malware does
On require() of the package, index.js loads init.js which selects a platform-specific asset path and downloads a native executable from Cloudflare Workers hosts whose names are reassembled from split string fragments (oob-worker.cf103-070.workers.dev, cf99-9b3, cf100-416), with a DNS TXT-chunked base64 fallback via *.dl.well1.site domains (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site). The downloaded payload is written to a temp path under a decoy name (dotnet_diag<hex>.exe on Windows,.cache_<hex> under /var/tmp on POSIX), chmod 0755'd via string-concatenated method name (fs['chmod'+'Sync']), and spawned detached via /bin/sh -c... & or cmd.exe /c start /b. The tarball also ships lib/telemetry.js (~81KB) containing a parallel dropper stage with the same primitives (base64 payload decoding, chmod 755, cp.spawn('/bin/sh',['-c',...])) wrapped in a fake analytics-SDK cover. Environment variables such as DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK are honored as a cover story to evade sandboxes and CI. The package name resembles a Tinkoff internal scope but the shipped code has no legitimate mobile-slider-icons functionality.
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-pfp-integration-mobile-slider-icons (version 20.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-pfp-integration-mobile-slider-icons across your stack and pipelines.
If you installed it — respond
tinkoff-pfp-integration-mobile-slider-icons 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-pfp-integration-mobile-slider-icons 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-integration-mobile-slider-icons 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-integration-mobile-slider-icons-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.