Abuse RadarThreat Intelligence

Connecting

Address

31.130.35.29

High 10/15/30d lists

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 score59/100
Detection volume+24Sensor corroboration+5Signal class+18Recency+12
Enrichment

Address intelligence

cached
CountryRussian FederationRU
City / regionMoscow, Moskva, Russian FederationEurope/Moscow
NetworkKom lan Ltddegunino.biz
ASNAS49583
Reverse DNS—
Detections6total observations
Reporting sensors1distinct collectors
First seen2026-05-24 11:55 GMT+84 months ago
Last seen2026-10-05 23:45 GMT+83 days ago
Blocklist window10/15/30d lists
Attribution

Reporting sensors

which collectors observed this address
  • Leak Trap Sensor 026 observations · last 2026-10-05 23:45 GMT+8Leak
Sensor names are anonymised. Collector hostnames and log contents are never published.
Signals

Observation history

1 signal record
  • Leak trap address contactedHighLeak trap
    6 detections from 1 sensor · first seen 2026-05-24 11:55 GMT+8 · last seen 2026-10-05 23:45 GMT+8 (3 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, 12 single-signal

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

Showing the 12 strongest of 29 related addresses, ranked by how much each shared value narrows the field.

  • 111.26.101.77Single-signal

    AS134810 Observed across 135 days, 3 detections recorded.

    • First observed together20 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T04:15:15+00:00Both addresses were first observed within 20 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 109.233.21.109Single-signal

    AS48847 Observed across 133 days, 4 detections recorded.

    • First observed together5 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T03:50:11+00:00Both addresses were first observed within 5 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 1.250.67.114Single-signal

    AS9318 Observed across 133 days, 8 detections recorded.

    • First observed together20 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T04:15:19+00:00Both addresses were first observed within 20 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 77.41.156.64Single-signal

    AS3216 Observed across 132 days, 7 detections recorded.

    • First observed together4 seconds apart2026-05-24T03:55:14+00:00 / 2026-05-24T03:55:10+00:00Both addresses were first observed within 0 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 183.82.56.12Single-signal

    AS55577 Observed across 126 days, 4 detections recorded.

    • First observed together20 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T04:15:24+00:00Both addresses were first observed within 20 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 174.134.45.64Single-signal

    AS33363 Observed across 125 days, 6 detections recorded.

    • First observed together20 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T03:35:13+00:00Both addresses were first observed within 20 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 94.190.15.13Single-signal

    AS48524 Observed across 116 days, 3 detections recorded.

    • First observed together10 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T03:45:12+00:00Both addresses were first observed within 10 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 112.27.129.78Single-signal

    AS9808 Observed across 109 days, 3 detections recorded.

    • First observed together10 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T03:45:14+00:00Both addresses were first observed within 10 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 153.35.192.98Single-signal

    AS4837 Observed across 107 days, 4 detections recorded.

    • First observed together20 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T03:35:10+00:00Both addresses were first observed within 20 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 60.29.128.122Single-signal

    AS4837 Observed across 106 days, 4 detections recorded.

    • First observed together20 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T04:15:17+00:00Both addresses were first observed within 20 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 177.159.150.111Single-signal

    AS18881 Observed across 103 days, 4 detections recorded.

    • First observed together5 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T03:50:16+00:00Both addresses were first observed within 5 minutes of each other (window is +/-30 minutes).distinguishing
    Open address
  • 219.248.65.30Single-signal

    AS9318 Observed across 100 days, 3 detections recorded.

    • First observed together20 minutes apart2026-05-24T03:55:14+00:00 / 2026-05-24T04:15:25+00:00Both addresses were first observed within 20 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.