Connecting

Address

34.159.132.5

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 score62/100
Detection volume+8Sensor corroboration+10Signal class+0Recency+12
Enrichment

Address intelligence

cached
CountryGermanyDE
City / regionFrankfurt am Main, Hessen, GermanyEurope/Berlin
NetworkGoogle LLCgoogle.com
ASNAS396982
Reverse DNS5.132.159.34.bc.googleusercontent.com
Detections33total observations
Reporting sensors5distinct collectors
First seen2026-10-06 02:06 GMT+83 days ago
Last seen2026-10-06 05:08 GMT+83 days ago
Blocklist window10/15/30d lists
Attribution

Reporting sensors

which collectors observed this address
  • Web Sensor 0229 observations · last 2026-10-06 05:08 GMT+8Web
  • Web Sensor 014 observations · last 2026-10-06 02:06 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 2 sensors · first seen 2026-10-06 02:06 GMT+8 · last seen 2026-10-06 05:08 GMT+8 (3 days 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 2 sensors · first seen 2026-10-06 02:06 GMT+8 · last seen 2026-10-06 05:08 GMT+8 (3 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
    25 detections from 1 sensor · first seen 2026-10-06 05:08 GMT+8 · last seen 2026-10-06 05:08 GMT+8 (3 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.

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.