ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.224.38

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-26 12:27:20
First seen: 2026-06-25 17:19:36
Last seen: 2026-06-27 23:57:24
100

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
173.239.224.38
Type
VPN
Country
🇺🇸 United States
City
Dallas
ISP
LogicWeb Inc
Organization
Unknown
Autonomous System
AS396356 Latitude.sh
Hit Count
181
02

Detection Signatures

SignatureDescriptionPointsSeverity
Directory ScanBehavioral anomaly detected by automated analysis+0
Σ = 0
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-06-25 17:19:36
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Directory Scan
2026-06-27 23:57:24
Last malicious request observed
Total score reached: 100/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

LogicWeb Inc
AS396356 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

⚙️ Defensive Recommendations

Block 173.239.224.38 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

07

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

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

10

Threat Analysis

173.239.224.38 has been assigned a threat score of 100/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

📊 Threat Analysis

The address 173.239.224.38 originates from Dallas, United States, operating on the network of LogicWeb Inc. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 181 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~90.5 requests per day. The address operates as a VPN/proxy exit node. Attackers route traffic through anonymizing services to obscure their real location and evade IP-based security controls. Our records show 13 malicious IPs originating from United States, positioning it as a notable contributor to global threat activity. A score of 100/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

11

Related Threats

🇺🇸 Top threats from United States

45.132.115.24 (110)172.98.33.9 (100)173.239.224.35 (100)173.239.224.43 (100)173.239.224.36 (100)View all →

🏢 Same network: AS396356

45.134.20.152 (280)45.134.20.92 (280)45.134.20.96 (280)45.134.20.126 (255)45.134.20.130 (255)View all →
12

Security Intelligence

💡 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.

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

🔍 Check Any IP Address

Share this report: