ABUSE.MOM
THREAT REPORT

IP Threat Report
52.165.255.19

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 21:40:53
First seen: 2026-05-07 00:00:06
Last seen: 2026-05-07 04:00:06
160

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 160/100. Total malicious requests observed: 3.

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
52.165.255.19
Type
Hosting
Country
🇺🇸 United States
City
Des Moines
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (centralus)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
3
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 4Medium-risk: admin panels, config files+40
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 6Medium-risk: admin panels, config files+60
Σ = 285
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-05-07 00:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 2 (+50), Danger medium hits: 4 (+40), 404 ratio 40-60% (+15)
2026-05-07 04:00:06
Last malicious request observed
Total score reached: 160/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 52.165.255.19 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 52.165.255.19 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net
✓ Clean
dnsbl-1.uceprotect.net

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

52.165.255.19 has been assigned a threat score of 160/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 52.165.255.19, geolocated to Des Moines, United States, operating on the network of Microsoft Corporation, as a source of suspicious network activity. Over a period of 1 days, this IP generated 3 malicious requests, averaging approximately 3 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 160/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS8075

74.241.249.229 (340)20.151.111.128 (308)4.182.24.88 (285)20.65.61.3 (283)4.205.39.97 (283)View all →
12

Security Intelligence

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

💡 Edge Computing Attack Surface

Edge computing pushes processing closer to users but expands the attack surface. Edge nodes often run in less secure environments than centralized data centers, creating new opportunities for physical access attacks and supply chain compromises.

🔍 Check Any IP Address

Share this report: