# MAL-2026-12231: Malicious code in tinkoff-boxy-form-desktop-sme-registration-ooo (npm)


- **Type:** Malicious package
- **Package:** `tinkoff-boxy-form-desktop-sme-registration-ooo` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-m24w-7xcq-wvr8

## What is MAL-2026-12231?

MAL-2026-12231 is a malicious package in tinkoff-boxy-form-desktop-sme-registration-ooo, published on 5 Aug 2026. 

### Official description

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.

## What should I do about MAL-2026-12231?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-12231 is a malicious package: tinkoff-boxy-form-desktop-sme-registration-ooo (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-12231/ (Markdown: https://insights.sbomify.com/MAL-2026-12231/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-12231

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-12231/
Summaries are generated and may contain mistakes; the official description above is the record.