Abuse RadarThreat Intelligence

Connecting

Address

34.156.22.222

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.

Request review Check AbuseIPDB JSON
Triage

Risk score

how this score is made up
Risk score55/100
Detection volume+45Sensor corroboration+10Signal class+0Recency+0
Enrichment

Address intelligence

cached
CountryBelgiumBE
City / regionBrussels, Bruxelles-Capitale, BelgiumEurope/Brussels
NetworkGoogle LLCgoogle.com
ASNAS396982
Reverse DNS222.22.156.34.bc.googleusercontent.com
Detections57total observations
Reporting sensors5distinct collectors
First seen2026-09-14 11:40 GMT+825 days ago
Last seen2026-09-21 20:38 GMT+818 days ago
Blocklist window30d list only
Attribution

Reporting sensors

which collectors observed this address
  • Web Sensor 0228 observations · last 2026-09-21 20:38 GMT+8Web
  • Web Sensor 0129 observations · last 2026-09-14 11:40 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
    50 detections from 2 sensors · first seen 2026-09-14 11:40 GMT+8 · last seen 2026-09-21 20:38 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.

  • Sensitive file probing over HTTPMediumWeb attack
    6 detections from 2 sensors · first seen 2026-09-14 11:40 GMT+8 · last seen 2026-09-21 20:38 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.

  • Known exploit path probing over HTTPLowWeb attack
    1 detection from 1 sensor · first seen 2026-09-14 11:40 GMT+8 · last seen 2026-09-14 11:40 GMT+8 (25 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.

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 255 related addresses, ranked by how much each shared value narrows the field.

  • 91.148.245.81Single-signal

    AS34343 Observed across 36 days, 66 detections recorded.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 81.171.74.60Single-signal

    AS34343 Observed across 35 days, 95 detections recorded.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 195.178.110.94Single-signal

    AS48090 Observed across 21 hours, 62 detections recorded.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 167.99.182.39Single-signal

    AS14061 Observed in a single observation window.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 138.68.144.227Single-signal

    AS14061 Observed in a single observation window.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 213.209.159.133Single-signal

    AS208137 Observed across 23 days, 414 detections recorded.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 34.156.22.151Single-signal

    AS396982 Observed across 16 days, 116 detections recorded.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 213.209.159.84Single-signal

    AS208137 Observed across 22 days, 323 detections recorded.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 91.148.244.131Single-signal

    AS34343 Observed across 31 days, 87 detections recorded.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 81.171.72.135Single-signal

    AS34343 Observed across 20 days, 149 detections recorded.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 81.171.72.93Single-signal

    AS34343 Observed across 25 days, 116 detections recorded.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    Open address
  • 34.81.48.65Single-signal

    AS396982 Observed across 9 hours, 65 detections recorded.

    • Same reasonweb_exploit_probeKnown exploit path probing over HTTPweb_exploit_probe appears on 108 observations (1.5% of the corpus).distinguishing
    • Same reasonweb_scanner_enumerationAutomated web path enumerationweb_scanner_enumeration appears on 211 observations (2.8% of the corpus).distinguishing
    • Same reasonweb_sensitive_file_probeSensitive file probing over HTTPweb_sensitive_file_probe appears on 383 observations (5.1% of the corpus).common
    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.