tinkoff-boxy-desktop-icons-horizontalnpm
tinkoff-boxy-desktop-icons-horizontal is a confirmed malicious npm package (MAL-2026-12228) that executes malicious code on install (malicious version 20.1.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-boxy-desktop-icons-horizontal (npm)
What this malware does
The package's index.js unconditionally requires compat.js, which on module load fetches an opaque native binary from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT chunked-base64 fallback via {tin,tina,ldr,win}.dl.well1.site. The downloaded bytes are written to /tmp or %TEMP% under a hidden dot-file or a dotnet_diag<hex>.exe name, chmod 0755, and spawned detached via cmd.exe /c start /b on Windows or /bin/sh -c on POSIX. No such binary is shipped in the tarball, no hash or signature is verified, and the destinations do not correspond to the publisher named in the package metadata. Host strings and the child_process require are assembled by fragment concatenation to evade static inspection, and the dropped file is named to resemble the.NET diagnostics tool. The visible library API is a trivial no-op class; the Tinkoff-branded name and 'desktop icons horizontal abstraction layer' description do not correspond to any functionality the package actually provides.
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-boxy-desktop-icons-horizontal (version 20.1.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-boxy-desktop-icons-horizontal across your stack and pipelines.
If you installed it — respond
Remove tinkoff-boxy-desktop-icons-horizontal 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-boxy-desktop-icons-horizontal 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-desktop-icons-horizontal 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-desktop-icons-horizontal-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.