ABUSE.MOM
THREAT REPORT

IP Threat Report
173.30.22.153

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-05 09:12:24
First seen: 2026-07-04 18:38:59
Last seen: 2026-07-05 04:02:51
60

⛔ Verdict: BLOCK

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

RATIO_404REDIRECT_PROBEUA_CHANGED
01

Geolocation & Classification

IP Address
173.30.22.153
Type
Residential
Country
🇺🇸 United States
City
Cromwell
ISP
Mediacom Communications
Organization
MEDIACOM
Autonomous System
AS30036 Mediacom Communications Corp
Hit Count
24
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 60
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-07-04 18:38:59
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Probe 302→404 (+20), UA changed (+25)
2026-07-05 04:02:51
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Mediacom Communications
AS30036 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 173.30.22.153 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • 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 173.30.22.153: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 Bot Detection

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

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org

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

10

Threat Analysis

173.30.22.153 has been assigned a threat score of 60/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

IP address 173.30.22.153 has been traced to Cromwell, United States, operating on the network of Mediacom Communications. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 1 days in our monitoring system, producing 24 flagged requests at a rate of ~24/day. 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 dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 102 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS30036

50.81.22.193 (80)View all →
12

Security Intelligence

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

💡 Passive DNS for Threat Hunting

Passive DNS databases record historical DNS resolution data, enabling analysts to track domain changes, identify related infrastructure, and discover malicious domains sharing hosting with known threats. This historical context is invaluable for threat investigation.

🔍 Check Any IP Address

Share this report: