ABUSE.MOM
THREAT REPORT

IP Threat Report
172.184.211.145

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-12 07:25:52
First seen: 2026-07-03 22:52:18
Last seen: 2026-07-12 00:28:14
178

⛔ Verdict: BLOCK

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

DANGER_PATHMETHODRATIO_404REFERERUA_CHANGED
01

Geolocation & Classification

IP Address
172.184.211.145
Type
Hosting
Country
🇺🇸 United States
City
San Francisco
ISP
Microsoft
Organization
Microsoft Azure Cloud (westus)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
267
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 253
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-07-03 22:52:18
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Danger medium hits: 2 (+20)
2026-07-12 00:28:14
Last malicious request observed
Total score reached: 178/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft
AS8075 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 172.184.211.145 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 172.184.211.0/24
  • 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 172.184.211.145 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 Bot Detection

Address UA spoofing from 172.184.211.145: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 172.184.211.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
cbl.abuseat.org
✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

172.184.211.145 has been assigned a threat score of 178/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

The address 172.184.211.145 originates from San Francisco, United States, operating on the network of Microsoft. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 8-day observation window, we recorded 267 hostile requests from this IP — roughly 33.4 per day on average. 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. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 104 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 178/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.214.122 (350)103.215.74.213 (340)103.168.66.237 (340)34.187.158.4 (340)View all →

🏢 Same network: AS8075

20.226.81.88 (280)20.48.26.146 (280)191.234.169.57 (280)52.237.113.70 (280)104.208.65.18 (280)View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 Network Telescope and Darknet Monitoring

Network telescopes monitor large blocks of unused IP address space. Since no legitimate traffic should reach these addresses, all observed traffic represents scanning, backscatter from spoofed attacks, or misconfiguration — providing pure signal for threat analysis.

🔍 Check Any IP Address

Share this report: