tinkoff-boxy-mobile-documentsnpm
tinkoff-boxy-mobile-documents is a confirmed malicious npm package (MAL-2026-12234) that typosquats a legitimate package to trick installs (malicious version 20.1.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-boxy-mobile-documents (npm)
What this malware does
On require of the package, index.js loads./platform.js, which selects a per-platform payload path, fetches an unsigned binary over HTTPS from string-split Cloudflare Workers subdomains (oob-worker.cf103-070.workers.dev, cf102-baf.workers.dev, cf101-adf.workers.dev, cf100-416.workers.dev) assembled via array joins, with a DNS TXT covert-channel fallback under *.dl.well1.site (also string-split). The fetched bytes are written to /tmp or %TEMP% under decoy names (analytics_state, dotnet_diag,.cache_), chmodded to 0755, and spawned detached via /bin/sh -c or cmd /c start. Hostnames and resolver domains are obfuscated by array joins and child_process is referenced as require('child_' + 'process'), and the loader is framed with 'analytics/telemetry' comments and DISABLE_TELEMETRY / ANALYTICS_OPT_OUT opt-out gates as cover. lib/telemetry.js contains a duplicate dropper implementation (base64 chunk assembly, cp.spawn('/bin/sh', ['-c', filePath + ' &']), chmod 0755 via computed property) bundled as an alternate loader. The package name impersonates a Tinkoff-branded mobile-documents component.
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-boxy-mobile-documents (version 20.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-boxy-mobile-documents across your stack and pipelines.
If you installed it — respond
tinkoff-boxy-mobile-documents is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-boxy-mobile-documents, 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-boxy-mobile-documents 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-boxy-mobile-documents 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-boxy-mobile-documents-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.