tinkoff-component-page-loadernpm
Advisory published Updated
tinkoff-component-page-loader is a confirmed malicious npm package (MAL-2026-12239) that steals credentials and exfiltrates sensitive data (malicious version 20.8.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-component-page-loader (npm)
What this malware does
On require() of the package, index.js loads platform.js which unconditionally invokes a setup routine that downloads a platform-specific binary from obfuscated Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT covert-channel fallback to *.dl.well1.site. Destination hostnames are assembled at runtime via split-string.join() to defeat static string matching. The downloaded bytes are written to /tmp or %TEMP% under disguised names such as dotnet_diag.exe and.cache_, chmodded 0755, and spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start /b. A persistence marker (.analytics_state) is written and OPT_OUT environment variables gate execution for evasion. No hash/signature verification is performed and the downloaded binary is unrelated to the advertised component-loader purpose. The package name typosquats Tinkoff. Result: arbitrary attacker-controlled code executes on the installer's host at require time.
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
Credential / info stealerFind it
Search your lockfiles and build artifacts for tinkoff-component-page-loader (version 20.8.2).
If you installed it — respond
tinkoff-component-page-loader 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-component-page-loader 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tinkoff-component-page-loader-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.