IP Threat Report
176.96.137.48
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 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 21 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 21 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 7 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 14 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 14 req / 10s | Abnormally fast request rate — automated scanning | +35 |
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 176.96.137.48 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
🤖 Bot Detection
Address UA spoofing from 176.96.137.48: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 176.96.137.48.
🔎 Directory Scan Defense
IP 176.96.137.48 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| CVE ID | Link |
|---|---|
| CVE-2024-38476 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2024-27316 | NVD → |
| CVE-2025-23048 | NVD → |
| CVE-2023-38709 | NVD → |
| CVE-2012-4360 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2024-43204 | NVD → |
| CVE-2024-38474 | NVD → |
| CVE-2025-55753 | NVD → |
| CVE-2009-2299 | NVD → |
| CVE-2007-4723 | NVD → |
| CVE-2024-24795 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2024-38477 | NVD → |
| CVE-2025-65082 | NVD → |
| CVE-2024-38475 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2024-38472 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2024-36387 | NVD → |
| CVE-2013-0941 | NVD → |
| CVE-2024-43394 | NVD → |
| CVE-2024-47252 | NVD → |
🔴 This host has 37 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
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
176.96.137.48 has been assigned a threat score of 95/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
176.96.137.48 is registered in Frankfurt am Main, Germany, operating on the network of dataforest GmbH. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 46-day observation window, we recorded 155 hostile requests from this IP — roughly 3.4 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. With 103 flagged addresses, Germany represents a significant presence in our threat database. With a threat score of 95/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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 Germany
15.220.152.241 (320)77.81.65.244 (313)185.168.29.98 (313)91.217.249.222 (305)212.30.36.219 (305)View all →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.
💡 Data Breach Impact Assessment
The impact of data breaches extends beyond immediate financial losses. Regulatory fines, legal liability, reputational damage, and customer churn create long-term costs that often exceed the direct costs of incident response and remediation.