Connecting

Address

139.59.143.102

High 30d list only

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 score50/100
Detection volume+45Sensor corroboration+5Signal class+0Recency+0
Enrichment

Address intelligence

cached
CountryGermanyDE
City / regionFrankfurt am Main, Hessen, GermanyEurope/Berlin
NetworkDigitalOcean, LLCdigitalocean.com
ASNAS14061
Reverse DNSf1096f7e4e.scan.leakix.org
Detections29total observations
Reporting sensors3distinct collectors
First seen2026-09-21 02:02 GMT+818 days ago
Last seen2026-09-21 02:02 GMT+818 days ago
Blocklist window30d list only
Attribution

Reporting sensors

which collectors observed this address
  • Web Sensor 0229 observations · last 2026-09-21 02:02 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
    25 detections from 1 sensor · first seen 2026-09-21 02:02 GMT+8 · last seen 2026-09-21 02:02 GMT+8 (18 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.

  • Known exploit path probing over HTTPLowWeb attack
    1 detection from 1 sensor · first seen 2026-09-21 02:02 GMT+8 · last seen 2026-09-21 02:02 GMT+8 (18 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 HTTPLowWeb attack
    3 detections from 1 sensor · first seen 2026-09-21 02:02 GMT+8 · last seen 2026-09-21 02:02 GMT+8 (18 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.

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.