Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

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)

MAL-2026-12227
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tinkoff-boxy-atom-text-link

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.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
20.5.9

Indicators of compromise (SHA-256)

3606d69d2c4891a247201742fcab0e3069060e9d669e537de5758c5a03279521
6fe3026e92e06237f9e92507433321a38b767f7bc13348e019c6825b23da4c44

Detection & response playbook

Malicious package
  1. Find 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.

  2. 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.

  3. 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.

  4. 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

No. tinkoff-boxy-atom-text-link on npm has been identified as a malicious package (version 20.5.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014485GHSA-wc79-x38v-pmr3

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.

Explore

tinkoff-boxy-atom-text-link (npm) malicious package — MAL-2026-12227 | O3 Security