ABUSE.MOM
THREAT REPORT

IP Threat Report
52.173.162.96

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 22:40:07
First seen: 2026-05-05 20:00:06
Last seen: 2026-05-05 23:00:06
113

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404METHODREFERER
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
POST requests presentBehavioral anomaly detected by automated analysis+8
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
Foreign referer seenReferer from unrelated external domain+10
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Σ = 238
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-05 20:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 1 (+25), Danger medium hits: 1 (+10), 404 ratio >= 60% (+25)
2026-05-05 23:00:06
Last malicious request observed
Total score reached: 113/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.173.162.96 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

🔎 Path Enumeration Protection

Block scanning from 52.173.162.96: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

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
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

52.173.162.96 has been assigned a threat score of 113/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

IP address 52.173.162.96 has been traced to Des Moines, United States, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 10 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~10 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 101 flagged addresses, United States represents a significant presence in our threat database. A score of 113/100 places this address in the top tier of severity. Block and investigate any historical connections.

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

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: