Connecting

Address

34.26.193.211

High 30d list only

Requests aimed at a specific known vulnerability, such as a PHPUnit eval endpoint or a router administration form. The request was made; nothing here says it worked.

Triage

Risk score

how this score is made up
Risk score60/100
Detection volume+16Sensor corroboration+15Signal class+0Recency+0
Enrichment

Address intelligence

cached
CountryUnited StatesUS
City / regionNorth Charleston, South Carolina, United StatesAmerica/New_York
NetworkGoogle LLCgoogle.com
ASNAS396982
Reverse DNS211.193.26.34.bc.googleusercontent.com
Detections124total observations
Reporting sensors11distinct collectors
First seen2026-09-14 02:46 GMT+825 days ago
Last seen2026-09-14 21:41 GMT+825 days ago
Blocklist window30d list only
Attribution

Reporting sensors

which collectors observed this address
  • Web Sensor 0259 observations · last 2026-09-14 21:41 GMT+8Web
  • Web Sensor 015 observations · last 2026-09-14 16:17 GMT+8Web
  • Web Sensor 0360 observations · last 2026-09-14 05:34 GMT+8Web
Sensor names are anonymised. Collector hostnames and log contents are never published.
Signals

Observation history

4 signal records
  • Known exploit path probing over HTTPMediumWeb attack
    4 detections from 3 sensors · first seen 2026-09-14 02:47 GMT+8 · last seen 2026-09-14 21:41 GMT+8 (25 days ago) · active

    Requests aimed at a specific known vulnerability, such as a PHPUnit eval endpoint or a router administration form. The request was made; nothing here says it worked.

  • Sensitive file probing over HTTPHighWeb attack
    15 detections from 3 sensors · first seen 2026-09-14 02:46 GMT+8 · last seen 2026-09-14 21:41 GMT+8 (25 days ago) · active

    Requests for files that exist only to be stolen - .env, .git internals, configuration and database backups. A web sensor reports this after several distinct such paths from one address, never after a single 404.

  • Automated web path enumerationHighWeb attack
    100 detections from 2 sensors · first seen 2026-09-14 02:46 GMT+8 · last seen 2026-09-14 21:41 GMT+8 (25 days ago) · active

    One address requesting many distinct non-existent paths in a short window - the shape of an automated scanner rather than a person.

  • Path traversal attempted over HTTPMediumWeb attack
    5 detections from 3 sensors · first seen 2026-09-14 02:46 GMT+8 · last seen 2026-09-14 21:41 GMT+8 (25 days ago) · active

    A request target containing directory traversal, including percent-encoded and double-encoded forms, after normalisation.

Abuse Radar publishes sanitized indicators only. Severity is a triage hint computed from detection volume, sensor corroboration, signal class and recency — it is not an attribution claim. See methodology.