tinkoff-pfp-block-mobile-advert-footernpm
tinkoff-pfp-block-mobile-advert-footer is a confirmed malicious npm package (MAL-2026-12248) that typosquats a legitimate package to trick installs (malicious version 20.3.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-pfp-block-mobile-advert-footer (npm)
What this malware does
On require() of index.js, the package silently loads bootstrap.js, which reconstructs attacker-controlled hostnames from split-string fragments (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, with a DNS-TXT base64 fallback via subdomains of dl.well1.site) and downloads an unsigned platform-specific binary over HTTPS. The binary is written to /var/tmp/.cache<rand> on Unix or %TEMP%/dotnet_diag_<rand>.exe on Windows (a masquerade as a.NET diagnostic tool), chmod 0755, and detached-spawned via /bin/sh -c or cmd /c start. Re-execution is throttled by a state file (/tmp/.analytics_state or %TEMP%/analytics_state) checked against a MAX_AGE window. The package name impersonates Tinkoff internal tooling; the only functional code beyond a stub API surface is the dropper. Host reconstruction via array joins and the DNS-TXT payload transport are anti-analysis evasion.
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
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-advert-footer (version 20.3.3). 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-advert-footer across your stack and pipelines.
If you installed it — respond
tinkoff-pfp-block-mobile-advert-footer is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-pfp-block-mobile-advert-footer, 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-advert-footer 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-advert-footer 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-advert-footer-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.