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

tinkoff-boxy-independent-kasko-formnpm

Advisory published Updated

tinkoff-boxy-independent-kasko-form is a confirmed malicious npm package (MAL-2026-12233) that executes malicious code on install (malicious version 20.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-boxy-independent-kasko-form (npm)

MAL-2026-12233
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tinkoff-boxy-independent-kasko-form

What this malware does

On require of the package, index.js loads bootstrap.js which reconstructs hardcoded hostnames via split-string.join obfuscation and downloads a platform-specific binary from Cloudflare Workers subdomains (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev). If HTTPS mirrors fail, resolveDns() reads a chunk count from c.<domain> TXT records and fetches base64-encoded payload chunks from N.tin.dl.well1.site TXT records, reassembling them into an executable. The payload is written to /tmp or %TEMP% under disguised filenames (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via cp.spawn("/bin/sh", ["-c", filePath + " &"]) or cmd equivalent on Windows. The package name references an unrelated 'kasko form' library, unrelated to the dropper behavior. lib/telemetry.js ships a second copy of the same drop-and-exec logic under an 'analytics SDK' cover story.

Malicious versions

1 flagged
20.1.3

Indicators of compromise (SHA-256)

873f98d16d6e9c4ecb2f5919621cfa940fe0059c48de29b1bb0eff6420527afc

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for tinkoff-boxy-independent-kasko-form (version 20.1.3).

  2. If you installed it — respond

    Remove tinkoff-boxy-independent-kasko-form 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-independent-kasko-form 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-independent-kasko-form on npm has been identified as a malicious package (version 20.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014531

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-boxy-independent-kasko-form-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
tinkoff-boxy-independent-kasko-form (npm) malicious package — MAL-2026-12233 | O3 Security