Abuse RadarThreat Intelligence

Connecting

Address

15.218.129.235

Medium 30d list only

A monitored leak-trap address was contacted. This suggests the sender may be using exposed or scraped address data.

Request review Check AbuseIPDB JSON
Triage

Risk score

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

Address intelligence

cached
CountryUnited StatesUS
City / regionWenatchee, Washington, United StatesAmerica/Los_Angeles
NetworkZiply Fiberziplyfiber.com
ASNAS20055
Reverse DNS—
Detections4total observations
Reporting sensors1distinct collectors
First seen2026-09-02 15:45 GMT+81 month ago
Last seen2026-09-16 13:26 GMT+823 days ago
Blocklist window30d list only
Attribution

Reporting sensors

which collectors observed this address
  • Leak Trap Sensor 024 observations · last 2026-09-16 13:26 GMT+8Leak
Sensor names are anonymised. Collector hostnames and log contents are never published.
Signals

Observation history

1 signal record
  • Leak trap address contactedMediumLeak trap
    4 detections from 1 sensor · first seen 2026-09-02 15:45 GMT+8 · last seen 2026-09-16 13:26 GMT+8 (23 days ago) · active

    A monitored leak-trap address was contacted. This suggests the sender may be using exposed or scraped address data.

Correlation0 multi-signal, 8 single-signal

Addresses sharing an observed attribute with this one. Arrival proximity uses a ±30 minute window around first observation.

  • 15.218.135.58Single-signal

    AS20055 Observed across 117 days, 6 detections recorded.

    • Same ASNAS20055Ziply FiberAS20055 holds 2 observed addresses (0.0% of geolocated observations).distinguishing
    Open address
  • 103.181.81.150Single-signal

    AS149229 Observed across 37 days, 3 detections recorded.

    • First observed together30 minutes apart2026-09-02T07:45:14+00:00 / 2026-09-02T07:15:14+00:00Both addresses were first observed within 30 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 151.20.43.187Single-signal

    AS1267 Observed across 6 days, 2 detections recorded.

    • First observed together20 minutes apart2026-09-02T07:45:14+00:00 / 2026-09-02T08:05:10+00:00Both addresses were first observed within 20 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 34.51.196.29Single-signal

    AS396982 Observed in a single observation window.

    • First observed together27 minutes apart2026-09-02T07:45:14+00:00 / 2026-09-02T08:12:20+00:00Both addresses were first observed within 27 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 58.58.42.246Single-signal

    AS4134 Observed in a single observation window.

    • First observed together20 minutes apart2026-09-02T07:45:14+00:00 / 2026-09-02T08:05:11+00:00Both addresses were first observed within 20 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 97.211.176.59Single-signal

    AS6167 Observed in a single observation window.

    • First observed together20 minutes apart2026-09-02T07:45:14+00:00 / 2026-09-02T08:05:10+00:00Both addresses were first observed within 20 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 14.155.251.242Single-signal

    AS4134 Observed in a single observation window.

    • First observed together15 minutes apart2026-09-02T07:45:14+00:00 / 2026-09-02T08:00:16+00:00Both addresses were first observed within 15 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 210.105.93.136Single-signal

    AS4766 Observed in a single observation window.

    • First observed together0 seconds apart2026-09-02T07:45:14+00:00 / 2026-09-02T07:45:14+00:00Both addresses were first observed within 0 minutes of each other (window is +/-30 minutes).distinguishing
    Open address

These are shared observations, not attribution. Abuse Radar does not claim common ownership, operation, coordination or intent between these addresses.

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.