tramvai-tinkoff-module-legacy-popupnpm
tramvai-tinkoff-module-legacy-popup is a confirmed malicious npm package (MAL-2026-12052) that typosquats a legitimate package to trick installs (malicious version 20.4.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tramvai-tinkoff-module-legacy-popup (npm)
What this malware does
On require() of tramvai-tinkoff-module-legacy-popup, index.js loads setup.js, which selects a platform-specific payload from a hardcoded binary map, fetches it over HTTPS from Cloudflare Workers hosts whose names are assembled via array-join string concatenation (oob-worker.cf101-adf.workers.dev, cf103-070.workers.dev, cf99-9b3.workers.dev), writes the response to a temp directory under masquerading names (e.g. dotnet_diag_.exe,.cache_), chmods it 0o755, and spawns it detached via /bin/sh or cmd. setup.js also implements a DNS-TXT covert-channel fallback: it reads a chunk count from a TXT record at c.<domain> and reassembles N base64 TXT chunks from 0.<domain>, 1.<domain>,... under tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site before executing the reconstructed binary. index.js itself exports only a stub class with no functionality matching the advertised 'tramvai tinkoff module' purpose; lib/telemetry.js contains a parallel unused dropper helper (cp.spawn(/bin/sh), fs.chmodSync 0o755). The package name impersonates the tramvai/tinkoff Russian-language OSS ecosystem.
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 tramvai-tinkoff-module-legacy-popup (version 20.4.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tramvai-tinkoff-module-legacy-popup across your stack and pipelines.
If you installed it — respond
tramvai-tinkoff-module-legacy-popup is a typosquat — you almost certainly intended a legitimately-named package. Remove tramvai-tinkoff-module-legacy-popup, 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 tramvai-tinkoff-module-legacy-popup 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 tramvai-tinkoff-module-legacy-popup 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 tramvai-tinkoff-module-legacy-popup-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.