Malicious code in tinkoff-statist-browser-typed-client-sme.reporting.reporting (npm)
The npm package tinkoff-statist-browser-typed-client-sme.reporting.reporting contained malicious code that executed attacker-controlled native binaries on installation or require(). The package used obfuscation techniques to fetch platform-specific payloads from Cloudflare Workers and DNS fallback domains, then executed them with elevated permissions.
- Disclosed
- Last updated
- Blast radius
- Any system that installed or required the malicious package; arbitrary code execution on host systems.
- Ecosystems
- Attack vectors
- Affected entities
- tinkoff-statist-browser-typed-client-sme.reporting.reportingnpm package containing malicious code
The npm package tinkoff-statist-browser-typed-client-sme.reporting.reporting was published with embedded malicious code designed to execute arbitrary native binaries on the host system. The package name was crafted to impersonate an internal Tinkoff scope, with unused telemetry code serving as cover.\n\nUpon installation or require(), the package's index.js loads vendor.js, which fetches platform-specific binary payloads from one of four Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev). Hostnames are assembled at runtime via string concatenation to evade static detection. DNS TXT-record fallback discovery is configured via tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site.\n\nThe fetched binary is written to a randomized temporary path with disguised names (.cache, dotnet_diag_.exe), made executable (chmod 0755 on POSIX), and executed detached via shell spawn. Sensitive API names (child_process, chmodSync) are reconstructed from array joins to defeat static code analysis. A 22822-second cooldown flag prevents repeated execution attempts.\n\nThe incident was identified by Amazon Inspector and credited to the OpenSSF malicious-packages project.
Indicators of compromise
- Packages
- tinkoff-statist-browser-typed-client-sme.reporting.reporting
- Domains
- oob-worker.cf102-baf.workers.dev
- oob-worker.cf100-416.workers.dev
- oob-worker.cf103-070.workers.dev
- oob-worker.cf99-9b3.workers.dev
- tin.dl.well1.site
- tina.dl.well1.site
- ldr.dl.well1.site
- win.dl.well1.site
Remediation
- Immediately uninstall the package: npm uninstall tinkoff-statist-browser-typed-client-sme.reporting.reporting
- Audit all systems where this package was installed for unauthorized processes, network connections, or persistence mechanisms
- Review npm audit logs and package-lock.json for installation history and affected projects
- Block outbound connections to the identified Cloudflare Workers domains and DNS fallback domains (oob-worker.cf*.workers.dev, tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site)
- Regenerate any credentials or secrets that may have been exposed on affected systems
- Update npm dependencies and use npm audit to identify and remediate any remaining malicious packages
Sources
- GitHub Advisory GHSA-gxjm-79h7-8p8q · GitHub Advisory Database
Cite this entry
"Malicious code in tinkoff-statist-browser-typed-client-sme.reporting.reporting (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-tinkoff-statist-browser-typed-client-sme-reporting-reporting-n-1bx5oq
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in santana-baileys (npm)
Malicious code discovered in santana-baileys npm package that covertly relays WhatsApp messaging data to an attacker-controlled endpoint (https://fiora.nixel.my.id/) via obfuscated character-code reconstruction in the message-send code path.
npmCompromised package - resolvedcritical
Malicious code in elephant-tusk-runner (npm)
The npm package elephant-tusk-runner contained malicious code that exposed a remote shell and remote code execution surface via an unauthenticated Express + WebSocket server binding to 0.0.0.0:4201 with fully open CORS. Any peer able to reach the port could execute arbitrary commands on the host.
npmCompromised package - resolvedcritical
Malicious code in @cats-cdf/browser-metrics-meter (npm)
The npm package @cats-cdf/browser-metrics-meter contained malicious code in its preinstall lifecycle script that exfiltrated system reconnaissance data (username, hostname, public IP) to an OAST collector domain. The package executed this behavior unconditionally on installation without consent or documented purpose.
npmCompromised package - resolvedcritical
Malicious code in @ks-video/kwai-player-web (npm)
The npm package @ks-video/kwai-player-web contained malicious code in its postinstall hook that exfiltrated system reconnaissance data (hostname, username, working directory, network interfaces, environment variable names) over plain HTTP to an unrelated third-party domain. The package has no legitimate relationship to the declared publisher Kwai/@ks-video.
npmCompromised package