ABUSE.MOM
THREAT REPORT

IP Threat Report
207.241.173.41

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-30 07:17:30
220

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REFERERUA_CHANGED
01

Geolocation & Classification

IP Address
207.241.173.41
Type
Residential
Country
🇺🇸 United States
City
Hauppauge
ISP
Globecomm Network Services Corporation
Organization
Globecomm Network Services Corporation
Autonomous System
Unknown
Hit Count
1668
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 116/10sAbnormally fast request rate — automated scanning+35
Burst 33/10sAbnormally fast request rate — automated scanning+35
Burst 33/2sAbnormally fast request rate — automated scanning+35
Burst 39/2sAbnormally fast request rate — automated scanning+35
Burst 47/2sAbnormally fast request rate — automated scanning+35
Burst 55/2sAbnormally fast request rate — automated scanning+35
Burst 61/2sAbnormally fast request rate — automated scanning+35
Burst 63/10sAbnormally fast request rate — automated scanning+35
Burst 63/2sAbnormally fast request rate — automated scanning+35
Burst 83/10sAbnormally fast request rate — automated scanning+35
Burst 84/10sAbnormally fast request rate — automated scanning+35
Burst: 102 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 29 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 45 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 46 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 50 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 83 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 132High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 36High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 66High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 96High-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
Σ = 1305
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 116/10s (+35)
2026-05-30 07:17:30
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.41 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

🔎 Directory Scan Defense

IP 207.241.173.41 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 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.41.

🤖 Bot Detection

Address UA spoofing from 207.241.173.41: 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
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org
✓ Clean
bl.blocklist.de

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

10

Threat Analysis

207.241.173.41 has been assigned a threat score of 220/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 207.241.173.41 to malicious activity originating from Hauppauge, United States, operating on the network of Globecomm Network Services Corporation. The address has been under observation since its initial detection. During its 13-day observation window, we recorded 1,668 hostile requests from this IP — roughly 128.3 per day on average. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 150 flagged addresses, United States represents a significant presence in our threat database. A score of 220/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.

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.

💡 Privacy-Preserving Threat Detection

Advanced techniques enable threat detection while minimizing privacy impact. Encrypted DNS, differential privacy in analytics, and federated learning for threat models allow effective security monitoring without unnecessary surveillance of legitimate user behavior.

🔍 Check Any IP Address

Share this report: