Abuse RadarThreat Intelligence

Connecting

Address

131.72.33.119

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

Address intelligence

cached
CountryBrazilBR
City / regionFontoura Xavier, Rio Grande do Sul, BrazilAmerica/Sao_Paulo
NetworkBOAVISTA- PROVEDOR DE INTERNET E INFORMATICA LTDA
ASNAS61711
Reverse DNS—
Detections1total observations
Reporting sensors1distinct collectors
First seen2026-09-23 00:25 GMT+818 days ago
Last seen2026-09-23 00:25 GMT+818 days ago
Blocklist window30d list only
Attribution

Reporting sensors

which collectors observed this address
  • Leak Trap Sensor 021 observation · last 2026-09-23 00:25 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
    1 detection from 1 sensor · first seen 2026-09-23 00:25 GMT+8 · last seen 2026-09-23 00:25 GMT+8 (18 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.

  • 34.45.85.134Single-signal

    AS396982 Observed across 5 hours, 40 detections recorded.

    • First observed together14 minutes apart2026-09-22T16:25:18+00:00 / 2026-09-22T16:11:35+00:00Both addresses were first observed within 14 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.