ABUSE.MOM
THREAT REPORT

IP Threat Report
172.98.33.11

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:58:45
First seen: 2026-03-11 19:00:05
Last seen: 2026-05-30 07:34:36
75

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERERUA_SUS
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Foreign refererReferer from unrelated external domain+10
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Σ = 85
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-03-11 19:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger medium hits: 1 (+10), Danger strong hits: 1 (+25)
2026-05-30 07:34:36
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

Latitude.sh
AS396356 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 172.98.33.11 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

🔎 Path Enumeration Protection

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

🤖 User-Agent Anomaly Defense

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

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
Spamhaus ZEN

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

10

Threat Analysis

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

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

172.98.33.11 is registered in Dallas, United States, operating on the network of Latitude.sh. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 79 days in our monitoring system, producing 79 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 Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. With 223 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)45.132.115.4 (305)View all →
12

Security Intelligence

💡 Brute Force Attack Mechanics

Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.

💡 GDPR and Threat Intelligence

Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.

🔍 Check Any IP Address

Share this report: