ABUSE.MOM
THREAT REPORT

IP Threat Report
207.241.173.38

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:18:36
First seen: 2026-05-16 17:00:07
Last seen: 2026-05-24 10:21:02
220

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REFERERUA_CHANGED
01

Geolocation & Classification

IP Address
207.241.173.38
Type
Residential
Country
🇺🇸 United States
City
Hauppauge
ISP
Globecomm Network Services Corporation
Organization
Globecomm Network Services Corporation
Autonomous System
Unknown
Hit Count
1038
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
Burst 30/2sAbnormally fast request rate — automated scanning+35
Burst 32/2sAbnormally fast request rate — automated scanning+35
Burst 39/2sAbnormally fast request rate — automated scanning+35
Burst 43/2sAbnormally fast request rate — automated scanning+35
Burst 46/10sAbnormally fast request rate — automated scanning+35
Burst 47/2sAbnormally fast request rate — automated scanning+35
Burst 50/2sAbnormally fast request rate — automated scanning+35
Burst 53/2sAbnormally fast request rate — automated scanning+35
Burst 54/10sAbnormally fast request rate — automated scanning+35
Burst 56/10sAbnormally fast request rate — automated scanning+35
Burst 62/2sAbnormally fast request rate — automated scanning+35
Burst 72/10sAbnormally fast request rate — automated scanning+35
Burst 80/10sAbnormally fast request rate — automated scanning+35
Burst 82/10sAbnormally fast request rate — automated scanning+35
Burst: 55 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 85 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 36High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 66High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 78High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
Foreign referer seenReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Σ = 970
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-05-16 17:00:07
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), Burst 30/2s (+35)
2026-05-24 10:21:02
Last malicious request observed
Total score reached: 220/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 207.241.173.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 207.241.173.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 207.241.173.38.

🤖 Bot Detection

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

07

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

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

10

Threat Analysis

207.241.173.38 has been assigned a threat score of 220/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 EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 207.241.173.38, geolocated to Hauppauge, United States, operating on the network of Globecomm Network Services Corporation, as a source of suspicious network activity. Our sensors captured 1,038 malicious requests from this address across a 7-day span, reflecting a sustained attack cadence of ~148.3 requests per 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 combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. United States currently accounts for 150 blocked IPs in our database, making it a significant source of malicious traffic. At 220/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

🔍 Check Any IP Address

Share this report: