Which versions of tinkoff-component-limits are malicious?

The following npm versions of tinkoff-component-limits are flagged malicious: 20.4.9. Treat any of these as compromised.

How do I remediate tinkoff-component-limits if I installed it?

Remove tinkoff-component-limits 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.

I already installed tinkoff-component-limits — how do I know if it already compromised me?

If tinkoff-component-limits 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.

Is tinkoff-component-limits part of a known attack campaign?

Yes — tinkoff-component-limits is associated with the IN-MAL-2026-014493 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find tinkoff-component-limits across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-component-limits (version 20.4.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-component-limits across your stack and pipelines.

Malicious package

tinkoff-component-limitsnpm

tinkoff-component-limits is a confirmed malicious npm package (MAL-2026-12238) that executes malicious code on install (malicious version 20.4.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-component-limits (npm)

MAL-2026-12238

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall tinkoff-component-limits

What this malware does

The package presents itself as a Tinkoff SDK but ships no legitimate functionality. On require(), index.js loads shim.js, which selects a platform-specific payload path, downloads a binary over HTTPS from hardcoded, string-split Cloudflare Workers subdomains (oob-worker.cf1030-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS-TXT fallback across tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The fetched bytes are written to /var/tmp or %TEMP% under disguised names such as.cache<hex> and dotnet_diag_<hex>.exe, chmod 0755'd, and spawned detached via /bin/sh -c or cmd. Hostnames are assembled from split fragments at runtime to evade string scanning.

Malicious versions

1 flagged

20.4.9

Indicators of compromise (SHA-256)

5e6bc0aab20cfeb6b8faa38c382fbf50d7675b65b0a56eea0977c45ae59ee7d7

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-component-limits (version 20.4.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-component-limits across your stack and pipelines.
If you installed it — respond
Remove tinkoff-component-limits 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.
Did it already run?
If tinkoff-component-limits 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.
How O3 protects you
O3 blocks tinkoff-component-limits 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-component-limits on npm has been identified as a malicious package (version 20.4.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014493

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-component-limits-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