IP Threat Report
196.51.38.200
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
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 196.51.38.200 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 196.51.38.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Directory Scan Defense
IP 196.51.38.200 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Neighbors in 196.51.38.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8800 | Unknown | Low | Service on port 8800 |
| CVE ID | Link |
|---|---|
| CVE-2016-10003 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2019-12528 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2019-12529 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2018-1000027 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2019-18679 | NVD → |
| CVE-2019-12523 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2018-19131 | NVD → |
🔴 Security scanning identified 57 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
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
196.51.38.200 has been assigned a threat score of 105/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:
📊 Threat Analysis
Our monitoring infrastructure has identified 196.51.38.200, geolocated to Tukwila, United States, operating on the network of DynaNode LLC, as a source of suspicious network activity. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 198 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 105/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.
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 →Security Intelligence
💡 Remote Code Execution (RCE)
RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.
💡 Subdomain Takeover Vulnerabilities
Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.