IP Threat Report
173.239.218.111
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 173.239.218.111 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 173.239.218.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 User-Agent Anomaly Defense
IP 173.239.218.111 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🔎 Path Enumeration Protection
Block scanning from 173.239.218.111: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Neighbors in 173.239.218.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
173.239.218.111 has been assigned a threat score of 90/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:
📊 Threat Analysis
Threat intelligence analysis has linked 173.239.218.111 to malicious activity originating from Los Angeles, United States, operating on the network of LogicWeb Inc. The address has been under observation since its initial detection. Our sensors captured 2 malicious requests from this address across a 20-day span, reflecting a sustained attack cadence of ~0.1 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 218 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 90/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
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 →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.
💡 GraphQL Security Risks
GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.