Abuse RadarThreat Intelligence

Connecting

Address

176.213.75.105

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

Address intelligence

cached
CountryRussian FederationRU
City / regionLipetsk, Lipetsk Oblast, Russian FederationEurope/Moscow
NetworkJSC ER-Telecom Holding Lipetsk branchertelecom.ru
ASNAS50498
Reverse DNS176x213x75x105.dynamic.lipetsk.ertelecom.ru
Detections2total observations
Reporting sensors1distinct collectors
First seen2026-09-13 07:00 GMT+827 days ago
Last seen2026-10-05 04:55 GMT+85 days ago
Blocklist window10/15/30d lists
Attribution

Reporting sensors

which collectors observed this address
  • Leak Trap Sensor 022 observations · last 2026-10-05 04:55 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
    2 detections from 1 sensor · first seen 2026-09-13 07:00 GMT+8 · last seen 2026-10-05 04:55 GMT+8 (5 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, 1 single-signal

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

  • 109.195.14.161Single-signal

    AS50498 Observed across 75 days, 3 detections recorded.

    • Same ASNAS50498JSC ER-Telecom Holding Lipetsk branchAS50498 holds 2 observed addresses (0.0% of geolocated observations).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.