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

tinkoff-statist-browser-typed-client-sme.rko.origsmartphonepaytb.common.mobile.eventsnpm

tinkoff-statist-browser-typed-client-sme.rko.origsmartphonepaytb.common.mobile.events is a confirmed malicious npm package (MAL-2026-12275) that typosquats a legitimate package to trick installs (malicious version 20.2.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-statist-browser-typed-client-sme.rko.origsmartphonepaytb.common.mobile.events (npm)

MAL-2026-12275
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tinkoff-statist-browser-typed-client-sme.rko.origsmartphonepaytb.common.mobile.events

What this malware does

The package's index.js unconditionally requires./loader, which on load fetches a platform-specific executable from Cloudflare Workers endpoints (oob-worker.cf10{0-3}-*.workers.dev) with a DNS TXT fallback under *.dl.well1.site. Destination hostnames are reconstructed at runtime from arrays of substrings joined together to evade static analysis. The fetched binary is written to /tmp or %TEMP% under decoy names (dotnet_diag*.exe, analytics_state), chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe, granting the remote operator arbitrary code execution on any host that installs or imports this package. The package name is a long typosquat-shaped identifier impersonating internal Tinkoff namespacing.

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

Indicators of compromise (SHA-256)

9e1202cc47d9e9135b8b86db17305d80e50b516ef5e77ebd1771a1c5184b6cb8
5ebb6575a404b62d32c6222c03be6723dd06426fa4f6eec5db58bb28ca115e7e

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-statist-browser-typed-client-sme.rko.origsmartphonepaytb.common.mobile.events (version 20.2.5). 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.origsmartphonepaytb.common.mobile.events across your stack and pipelines.

  2. If you installed it — respond

    tinkoff-statist-browser-typed-client-sme.rko.origsmartphonepaytb.common.mobile.events is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-sme.rko.origsmartphonepaytb.common.mobile.events, 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-statist-browser-typed-client-sme.rko.origsmartphonepaytb.common.mobile.events 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.origsmartphonepaytb.common.mobile.events 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.origsmartphonepaytb.common.mobile.events on npm has been identified as a malicious package (version 20.2.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014501GHSA-8w68-xhpf-ww9j

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-statist-browser-typed-client-sme.rko.origsmartphonepaytb.common.mobile.events-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.origsmartphonepaytb.common.mobile.events (npm) malicious package — MAL-2026-12275 | O3 Security