Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

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

The npm package statist-browser-typed-client-sme.rko.tariffs.web contained malicious code that downloads and executes arbitrary binaries from attacker-controlled infrastructure upon require(). The package was identified by Amazon Inspector and credited to OpenSSF's malicious-packages repository.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any developer or application that installed the malicious package version(s) would execute arbitrary code on their system upon require().
Ecosystems
Attack vectors
Affected entities
  • statist-browser-typed-client-sme.rko.tariffs.webnpm package containing malicious code in index.js

The npm package statist-browser-typed-client-sme.rko.tariffs.web contained malicious code designed to execute arbitrary binaries on systems where the package was installed. Upon require(), the index.js file loads compat.js, which determines the target platform and fetches an opaque binary payload from one of three obfuscated Cloudflare Workers domains (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev).\n\nIf HTTPS delivery fails, the malware falls back to a DNS TXT covert channel using domains under *.dl.well1.site (tin/tina/ldr/win.dl.well1.site). The fetched binary is written to a temporary file with a benign cover-story name (dotnet_diag.exe on Windows, /var/tmp/.cache_ on Unix), given execute permissions (chmod 0755), and spawned detached via shell commands (/bin/sh -c on Unix, cmd /c start on Windows).\n\nThe malware employs obfuscation techniques including runtime assembly of C2 hostnames from split-string arrays to evade static analysis. No signature or hash verification is performed on the downloaded payload. A cooldown marker is written to suppress re-execution. The package's stated purpose as a 'web adapter' bears no relation to its actual malicious functionality.\n\nThe incident was identified by Amazon Inspector and credited to the OpenSSF's malicious-packages repository (MAL-2026-13379).

Indicators of compromise

Packages
  • statist-browser-typed-client-sme.rko.tariffs.web
Domains
  • oob-worker.cf100-416.workers.dev
  • oob-worker.cf99-9b3.workers.dev
  • oob-worker.cf101-adf.workers.dev
  • tin.dl.well1.site
  • tina.dl.well1.site
  • ldr.dl.well1.site
  • win.dl.well1.site

Remediation

  • Immediately remove the statist-browser-typed-client-sme.rko.tariffs.web package from all projects and environments
  • Audit package.json and lock files (package-lock.json, yarn.lock) for any presence of this package
  • Review npm install logs and dependency trees to identify all affected systems and applications
  • Perform forensic analysis on any systems where this package was installed, looking for unexpected processes, temporary files (dotnet_diag_*.exe, /var/tmp/.cache_*), and network connections to the identified C2 domains
  • Block outbound connections to the identified C2 infrastructure: oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, and *.dl.well1.site
  • Implement npm package scanning and verification in CI/CD pipelines to detect malicious packages before installation
  • Monitor for similar typosquatting or obfuscated package names that may indicate related malicious packages

Sources

  1. GitHub Advisory GHSA-3pph-9426-8xmv · GitHub Advisory Database

Cite this entry

"Malicious code in statist-browser-typed-client-sme.rko.tariffs.web (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 6, 2026; last updated August 6, 2026. https://supplychainattack.org/incident/malicious-code-in-statist-browser-typed-client-sme-rko-tariffs-web-npm-153m5p

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malicious code in autbank-core (npm)

    The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.

    npmCompromised package
  2. resolvedcritical

    Malicious code in adxaa (npm)

    The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.

    npmCompromised package
  3. resolvedcritical

    Malicious code in upload-to-gcp (npm)

    upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.

    npmCompromised package
  4. resolvedcritical

    Malicious code in akamai-sensor (npm)

    A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.

    npmCompromised packageTyposquatting