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

tinkoff-boxy-form-desktop-sme-registration-ooonpm

tinkoff-boxy-form-desktop-sme-registration-ooo is a confirmed malicious npm package (MAL-2026-12231) that typosquats a legitimate package to trick installs (malicious version 20.4.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-boxy-form-desktop-sme-registration-ooo (npm)

MAL-2026-12231
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tinkoff-boxy-form-desktop-sme-registration-ooo

What this malware does

Package name typosquats Tinkoff's official SME registration form. On require() of the package, index.js loads ext.js, which reconstructs attacker-controlled hostnames from string fragments (e.g. 'oob-worker.cf101-adf.workers.dev' and 'tin.dl.well1.site'), fetches a platform-specific binary over HTTPS, and falls back to reconstructing the payload from base64 chunks served in DNS TXT records under *.dl.well1.site when HTTPS is unavailable. The fetched bytes are written to /tmp or %TEMP% under disguised filenames (dotnet_diag<rand>.exe,.cache_<rand>, loader_mac), marked executable with chmod 0755 on Unix, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &']) on Unix or cp.spawn('cmd.exe', ['/c', 'start', '/b', fp]) on Windows. The dropper is unrelated to the package's advertised purpose as a form/SDK.

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

Indicators of compromise (SHA-256)

bd92a77dddf46c2afa43b4db0127eea04dfde2afa2ba45e7c43965c06249997e
4e7f2314074bad2d98a5a8d28925b7bd56de4fea7d43c7eff17ba2981f7c913e

Detection & response playbook

Typosquat
  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-form-desktop-sme-registration-ooo (version 20.4.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-boxy-form-desktop-sme-registration-ooo across your stack and pipelines.

  2. If you installed it — respond

    tinkoff-boxy-form-desktop-sme-registration-ooo is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-boxy-form-desktop-sme-registration-ooo, 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-form-desktop-sme-registration-ooo 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-form-desktop-sme-registration-ooo 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-form-desktop-sme-registration-ooo on npm has been identified as a malicious package (version 20.4.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014452GHSA-m24w-7xcq-wvr8

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-boxy-form-desktop-sme-registration-ooo-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