NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

tinkoff-boxy-mobile-documentsnpm

Advisory published Updated

tinkoff-boxy-mobile-documents is a confirmed malicious npm package (MAL-2026-12234) that typosquats a legitimate package to trick installs (malicious version 20.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-boxy-mobile-documents (npm)

MAL-2026-12234
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tinkoff-boxy-mobile-documents

What this malware does

On require of the package, index.js loads./platform.js, which selects a per-platform payload path, fetches an unsigned binary over HTTPS from string-split Cloudflare Workers subdomains (oob-worker.cf103-070.workers.dev, cf102-baf.workers.dev, cf101-adf.workers.dev, cf100-416.workers.dev) assembled via array joins, with a DNS TXT covert-channel fallback under *.dl.well1.site (also string-split). The fetched bytes are written to /tmp or %TEMP% under decoy names (analytics_state, dotnet_diag,.cache_), chmodded to 0755, and spawned detached via /bin/sh -c or cmd /c start. Hostnames and resolver domains are obfuscated by array joins and child_process is referenced as require('child_' + 'process'), and the loader is framed with 'analytics/telemetry' comments and DISABLE_TELEMETRY / ANALYTICS_OPT_OUT opt-out gates as cover. lib/telemetry.js contains a duplicate dropper implementation (base64 chunk assembly, cp.spawn('/bin/sh', ['-c', filePath + ' &']), chmod 0755 via computed property) bundled as an alternate loader. The package name impersonates a Tinkoff-branded mobile-documents component.

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

Indicators of compromise (SHA-256)

0975c5e634ca65495f0ec35088db60ae98702849f5f2fb31e2ad1d8eee2068b7
358ce3aca715709429ebd1b0bbf70ac94f65bbb01c60cac89f14386d7a56317f

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for tinkoff-boxy-mobile-documents (version 20.1.7).

  2. If you installed it — respond

    tinkoff-boxy-mobile-documents is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-boxy-mobile-documents, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If tinkoff-boxy-mobile-documents was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-014532GHSA-97hc-v95m-g3h9

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-boxy-mobile-documents-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-mobile-documents (npm) malicious package — MAL-2026-12234 | O3 Security