ABUSE.MOM
THREAT REPORT

IP Threat Report
172.200.23.68

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-26 11:20:30
First seen: 2026-07-23 00:17:54
Last seen: 2026-07-26 04:05:25
178

⛔ Verdict: BLOCK

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

DANGER_PATHMETHODRATIO_404REFERERUA_CHANGED
01

Geolocation & Classification

IP Address
172.200.23.68
Type
Hosting
Country
🇺🇸 United States
City
Boydton
ISP
Microsoft
Organization
Microsoft Azure Cloud (eastus2)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
306
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-23 00:17:54
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-26 04:05:25
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.200.23.68 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.200.23.0/24
  • 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 172.200.23.68: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 User-Agent Anomaly Defense

IP 172.200.23.68 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

07

Neighbors in 172.200.23.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
bl.spamcop.net
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
zen.spamhaus.org
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net

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

10

Threat Analysis

172.200.23.68 has been assigned a threat score of 178/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 EnumerationUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 172.200.23.68, geolocated to Boydton, United States, operating on the network of Microsoft, as a source of suspicious network activity. Our sensors captured 306 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~102 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 118 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 178/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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

💡 Cross-Site Scripting (XSS) Attacks

XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.

💡 Multi-Factor Authentication Importance

MFA dramatically reduces the effectiveness of credential-based attacks. Even when passwords are compromised through phishing or data breaches, the additional authentication factor prevents unauthorized access in the vast majority of cases.

🔍 Check Any IP Address

Share this report: