Connecting

Address

213.209.159.133

High 10/15/30d lists

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

Triage

Risk score

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

Address intelligence

cached
CountryGermanyDE
City / regionAugsburg, Bavaria, GermanyEurope/Berlin
NetworkFEO PREST SRLfeoprest.life
ASNAS208137
Reverse DNS—
Detections414total observations
Reporting sensors9distinct collectors
First seen2026-09-12 22:11 GMT+826 days ago
Last seen2026-10-06 13:34 GMT+83 days ago
Blocklist window10/15/30d lists
Attribution

Reporting sensors

which collectors observed this address
  • Web Sensor 0170 observations · last 2026-10-06 13:34 GMT+8Web
  • Web Sensor 02145 observations · last 2026-10-04 14:58 GMT+8Web
  • Web Sensor 03199 observations · last 2026-10-03 07:43 GMT+8Web
Sensor names are anonymised. Collector hostnames and log contents are never published.
Signals

Observation history

3 signal records
  • Automated web path enumerationHighWeb attack
    350 detections from 3 sensors · first seen 2026-09-12 22:11 GMT+8 · last seen 2026-10-06 13:34 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.

  • Sensitive file probing over HTTPHighWeb attack
    48 detections from 3 sensors · first seen 2026-09-18 06:07 GMT+8 · last seen 2026-10-06 13:34 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.

  • Known exploit path probing over HTTPHighWeb attack
    16 detections from 3 sensors · first seen 2026-09-18 06:07 GMT+8 · last seen 2026-10-06 13:34 GMT+8 (3 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.

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.