Connecting

Address

34.95.209.124

High 10/15/30d lists

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

Triage

Risk score

how this score is made up
Risk score70/100
Detection volume+8Sensor corroboration+5Signal class+0Recency+20
Enrichment

Address intelligence

cached
CountryBrazilBR
City / regionSao Paulo, Sao Paulo, BrazilAmerica/Sao_Paulo
NetworkGoogle LLCgoogle.com
ASNAS396982
Reverse DNS124.209.95.34.bc.googleusercontent.com
Detections58total observations
Reporting sensors3distinct collectors
First seen2026-10-10 03:19 GMT+81 hour ago
Last seen2026-10-10 04:20 GMT+851 minutes ago
Blocklist window10/15/30d lists
Attribution

Reporting sensors

which collectors observed this address
  • Web Sensor 0358 observations · last 2026-10-10 04:20 GMT+8Web
Sensor names are anonymised. Collector hostnames and log contents are never published.
Signals

Observation history

3 signal records
  • Path traversal attempted over HTTPMediumWeb attack
    2 detections from 1 sensor · first seen 2026-10-10 03:19 GMT+8 · last seen 2026-10-10 04:20 GMT+8 (51 minutes ago) · active

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

  • Sensitive file probing over HTTPMediumWeb attack
    6 detections from 1 sensor · first seen 2026-10-10 03:19 GMT+8 · last seen 2026-10-10 04:20 GMT+8 (51 minutes 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
    50 detections from 1 sensor · first seen 2026-10-10 03:19 GMT+8 · last seen 2026-10-10 04:20 GMT+8 (51 minutes ago) · active

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

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.