tinkoff-boxy-desktop-features-bannernpm
tinkoff-boxy-desktop-features-banner is a confirmed malicious npm package (MAL-2026-12048) that executes malicious code on install (malicious version 20.2.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-boxy-desktop-features-banner (npm)
What this malware does
The package's main entry (index.js) requires./setup at load time. setup.js assembles obfuscated Cloudflare Workers hostnames via array-join concatenation (e.g. oob-worker.cf99-9b3.workers.dev, cf103-070/cf102-baf/cf101-adf.workers.dev) with a DNS TXT fallback resolving through tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site, downloads a platform-specific binary payload with no hash or signature verification, writes it to /tmp or %TEMP% under a disguised filename, chmods it to 0755, and spawns it detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) (or cmd on Windows). A second module lib/telemetry.js (framed as an 'Analytics SDK') bundles the same dropper primitives with additional evasion (require('child_' + 'process'), fs['chmod' + 'Sync']). The remote destinations, obfuscated hostname assembly, and executed payload are unrelated to the package's stated 'features banner' purpose.
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-features-banner (version 20.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-boxy-desktop-features-banner across your stack and pipelines.
If you installed it — respond
Remove tinkoff-boxy-desktop-features-banner 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-features-banner 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-features-banner 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-features-banner-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.