tinkoff-pwa-confac-typesnpm
tinkoff-pwa-confac-types is a confirmed malicious npm package (MAL-2026-12252) that executes malicious code on install (malicious version 20.7.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-pwa-confac-types (npm)
What this malware does
The package advertises itself as a types interface but its main entry silently requires _adapter.js inside a try/catch. On require, adapter.js assembles obfuscated Cloudflare Workers hostnames by array-join (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT chunked base64 fallback across tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site, downloads a platform-specific binary, writes it to /var/tmp (hidden dot-file name) or %TEMP% (disguised as dotnet_diag*.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. child_process is required lazily inside the activation path and the dropper honors DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK as a cover story. No native source ships in the tarball and the behavior is unrelated to any 'types' functionality. An unreferenced 81 KB lib/telemetry.js is present as additional staging.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-pwa-confac-types (version 20.7.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-pwa-confac-types across your stack and pipelines.
If you installed it — respond
Remove tinkoff-pwa-confac-types from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tinkoff-pwa-confac-types 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-pwa-confac-types 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-pwa-confac-types-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.