tinkoff-boxy-atom-text-linknpm
tinkoff-boxy-atom-text-link is a confirmed malicious npm package (MAL-2026-12227) that executes malicious code on install (malicious version 20.5.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-boxy-atom-text-link (npm)
What this malware does
The package's index.js unconditionally requires./loader on module load. loader.js selects a platform-specific payload path and fetches bytes from one of three hardcoded Cloudflare Workers hosts whose names are assembled from split string fragments (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT covert-channel fallback across tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site that reads a chunk count from c.<domain> and reassembles base64-encoded payload bytes from N.<domain> TXT records. The fetched bytes are written to a temp file with a decoy name (dotnet_diag*.exe /.cache*), chmod 0755 on POSIX, and spawned detached via /bin/sh -c "<file> &" or cmd.exe /c start. A /tmp/.analytics_state marker rate-limits re-execution. A secondary module lib/telemetry.js bundled in the tarball replicates the same drop-and-exec primitives (string-split require of child_process, bracket-property chmodSync, base64 buffer decode, cp.spawn("/bin/sh", ["-c", filePath + " &"])). The package is advertised as a text-link provider; the shipped code has no relation to that 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-atom-text-link (version 20.5.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-boxy-atom-text-link across your stack and pipelines.
If you installed it — respond
Remove tinkoff-boxy-atom-text-link 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-atom-text-link 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-atom-text-link 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-atom-text-link-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.