ABUSE.MOM
THREAT REPORT

IP Threat Report
172.98.33.176

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 01:20:51
First seen: 2026-05-09 02:00:06
Last seen: 2026-05-09 02:00:06
75

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
172.98.33.176
Type
Residential
Country
🇺🇸 United States
City
Dallas
ISP
LayerSwitch
Organization
Prefixx, Inc
Autonomous System
AS396356 Latitude.sh
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
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
Σ = 75
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-09 02:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA suspicious (short/empty) (+15), Danger strong hits: 1 (+25), Danger medium hits: 1 (+10)
2026-05-09 02:00:06
Last malicious request observed
Total score reached: 75/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

LayerSwitch
AS396356 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 172.98.33.176 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.98.33.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

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

🔎 Path Enumeration Protection

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

07

Neighbors in 172.98.33.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.

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

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

10

Threat Analysis

172.98.33.176 has been assigned a threat score of 75/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.

The following attack categories were identified:

User-Agent AnomalyPath Enumeration

📊 Threat Analysis

Network traffic from 172.98.33.176, located in Dallas, United States, operating on the network of LayerSwitch, has been classified as malicious by our automated threat scoring engine. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. With 222 flagged addresses, United States represents a significant presence in our threat database. At 75/100, this IP warrants immediate defensive action.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

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: AS396356

173.239.224.82 (320)185.223.152.42 (320)185.223.152.45 (320)185.223.152.53 (305)185.223.152.61 (305)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 CORS Misconfiguration Exploitation

Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.

🔍 Check Any IP Address

Share this report: