tinkoff-boxy-desktop-two-panel-right-imagenpm
tinkoff-boxy-desktop-two-panel-right-image is a confirmed malicious npm package (MAL-2026-12230) that executes malicious code on install (malicious version 20.4.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-boxy-desktop-two-panel-right-image (npm)
What this malware does
On require of this package, index.js loads vendor.js which detects the host OS/arch, assembles destination hostnames from split string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), downloads a platform-specific binary via https.get, and falls back to a covert channel that reconstructs a base64 payload from numbered DNS TXT records under tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site. The retrieved bytes are written to /tmp or %TEMP% under decoy names such as.cache<hex> or dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via spawn('/bin/sh', ['-c', <path>+' &']) or cmd.exe /c start /b. A second module lib/telemetry.js, framed as an analytics SDK, ships the same base64-decode / chmodSync 0755 / detached spawn chain. The destinations are anonymous Cloudflare Workers subdomains and an unrelated DDNS-style domain; the fetched content is opaque native code executed on the installer's host with no verification.
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-two-panel-right-image (version 20.4.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-two-panel-right-image across your stack and pipelines.
If you installed it — respond
Remove tinkoff-boxy-desktop-two-panel-right-image 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-two-panel-right-image 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-two-panel-right-image 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-two-panel-right-image-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.