tinkoff-component-infopanelnpm
tinkoff-component-infopanel is a confirmed malicious npm package (MAL-2026-12049) that typosquats a legitimate package to trick installs (malicious version 20.8.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-component-infopanel (npm)
What this malware does
On require of the package, platform.js downloads a platform-specific native binary from hardcoded Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback resolved via *.dl.well1.site, writes the bytes to a masqueraded cache path (cover-story names such as dotnet_diag,.cache_,.analytics_state), chmods 0o755, and spawns it detached via /bin/sh -c or cmd. The destination hostnames are assembled at runtime by joining string fragments (e.g. ["oob-worker.cf10","0-416",".wo","rker","s.dev"].join("")) to evade static matching. No hash or signature verification is performed. The package name impersonates the Tinkoff brand while package.json declares an empty author, no repository, and a README labeling it an 'internal' module. The dropper fires via top-level require() from index.js, so importing this package as a dependency executes the fetched binary on the installer's host.
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-component-infopanel (version 20.8.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-component-infopanel across your stack and pipelines.
If you installed it — respond
tinkoff-component-infopanel is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-component-infopanel, 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-component-infopanel 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-component-infopanel 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-component-infopanel-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.