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

tinkoff-statist-browser-typed-client-sme.rko.conversionpayments.webnpm

tinkoff-statist-browser-typed-client-sme.rko.conversionpayments.web is a confirmed malicious npm package (MAL-2026-12274) that executes malicious code on install (malicious version 20.3.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-statist-browser-typed-client-sme.rko.conversionpayments.web (npm)

MAL-2026-12274
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tinkoff-statist-browser-typed-client-sme.rko.conversionpayments.web

What this malware does

On require of the package, index.js loads bridge.js which selects a platform-specific binary URL and races HTTP GETs across three Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS TXT fallback via tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The destination hostnames are assembled at runtime by splitting strings and joining them to evade static scanners. The fetched opaque bytes are written to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755'd, and detached-spawned via /bin/sh -c or cmd.exe /c start. lib/telemetry.js ships a second copy of the same write-chmod-spawn dropper, additionally hiding child_process behind require("child_" + "process") and fs["chmod" + "Sync"] method-name concatenation, and framing the payload as an analytics SDK. There is no pinning, no hash or signature verification of the fetched executable, and the destinations are author-controlled Cloudflare Workers subdomains obfuscated in source — behavior consistent with a supply-chain dropper delivering arbitrary attacker-controlled code to the installer's host on require.

Malicious versions

1 flagged
20.3.8

Indicators of compromise (SHA-256)

aedad3d882cc46a8a5a8189109dd03f3943c887644c308bee19791663c93a237

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-statist-browser-typed-client-sme.rko.conversionpayments.web (version 20.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-statist-browser-typed-client-sme.rko.conversionpayments.web across your stack and pipelines.

  2. If you installed it — respond

    Remove tinkoff-statist-browser-typed-client-sme.rko.conversionpayments.web 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-statist-browser-typed-client-sme.rko.conversionpayments.web 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-statist-browser-typed-client-sme.rko.conversionpayments.web 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-statist-browser-typed-client-sme.rko.conversionpayments.web on npm has been identified as a malicious package (version 20.3.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014514

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-statist-browser-typed-client-sme.rko.conversionpayments.web-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-statist-browser-typed-client-sme.rko.conversionpayments.web (npm) malicious package — MAL-2026-12274 | O3 Security