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

tinkoff-statist-browser-typed-client-sme.reporting.reportingnpm

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

Malicious code in tinkoff-statist-browser-typed-client-sme.reporting.reporting (npm)

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

What this malware does

The package executes a hidden loader when it is imported. The loader downloads and runs a platform-specific native payload from attacker-controlled Cloudflare Workers hosts, or reconstructs the payload from DNS TXT records under well1.site if HTTPS delivery fails. Systems that imported this package should be considered compromised; rotate accessible secrets and investigate temporary-file execution and DNS activity to the listed infrastructure.

On require() of the package, index.js loads vendor.js which selects a platform-specific endpoint and fetches a binary payload from one of four Cloudflare Workers hosts whose names are assembled at runtime via string split/join concatenation (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev), with DNS TXT-record fallback discovery via tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The fetched bytes are written to a randomized temp path with disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755 on POSIX, and executed detached via spawn("/bin/sh", ["-c", fp + " &"]) or spawn("cmd",...) on Windows. Hostnames and sensitive API names (child_process, chmodSync) are reconstructed from array joins to defeat static matching; a 22822-second cooldown flag suppresses re-execution. The package name imitates an internal Tinkoff scope while lib/telemetry.js is unused cover-story code. Installing or requiring this package executes attacker-controlled native code on the host.

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

Indicators of compromise (SHA-256)

eb2aa808aabae01f3ce4f8ed4a73077d3adffbbcdc1af80af27d6cc9de628d0e
76ed57d756e98153b854d31d8e645c67e786f15729180b1bef3ccec11b6f9429

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.reporting.reporting (version 20.5.4). 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.reporting.reporting across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-011480GHSA-hh5q-m44v-j748

References

Credits

  • Amazon Inspector · finder
  • skb1209 · finder

Detect & block this

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