IP Threat Report
200.59.191.102
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| 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 200.59.191.102 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 200.59.191.102: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 2000 | Unknown | Low | Service on port 2000 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8111 | Unknown | Low | Service on port 8111 |
| 8112 | Unknown | Low | Service on port 8112 |
| 8122 | Unknown | Low | Service on port 8122 |
| 8123 | Unknown | Low | Service on port 8123 |
| 8131 | Unknown | Low | Service on port 8131 |
| 8728 | Unknown | Low | Service on port 8728 |
| CVE ID | Link |
|---|---|
| CVE-2022-4900 | NVD → |
| CVE-2019-11048 | NVD → |
| CVE-2020-7059 | NVD → |
| CVE-2019-13224 | NVD → |
| CVE-2022-31628 | NVD → |
| CVE-2020-7066 | NVD → |
| CVE-2020-7067 | NVD → |
| CVE-2022-31629 | NVD → |
| CVE-2020-7061 | NVD → |
| CVE-2020-7060 | NVD → |
| CVE-2020-7069 | NVD → |
| CVE-2019-11072 | NVD → |
| CVE-2024-25117 | NVD → |
| CVE-2019-11047 | NVD → |
| CVE-2019-11046 | NVD → |
| CVE-2024-3566 | NVD → |
| CVE-2007-3205 | NVD → |
| CVE-2020-7063 | NVD → |
| CVE-2019-11050 | NVD → |
| CVE-2020-7068 | NVD → |
| CVE-2019-11043 | NVD → |
| CVE-2013-2220 | NVD → |
| CVE-2022-37454 | NVD → |
| CVE-2020-7064 | NVD → |
| CVE-2020-7062 | NVD → |
🔴 Security scanning identified 30 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
200.59.191.102 has been assigned a threat score of 60/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.
The following attack categories were identified:
📊 Threat Analysis
Our monitoring infrastructure has identified 200.59.191.102, geolocated to Valera, VE, operating on the network of TotalCom Venezuela C.A., as a source of suspicious network activity. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 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 IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. VE currently accounts for 70 blocked IPs in our database, making it a notable source of malicious traffic. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
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 VE
38.43.209.82 (233)45.173.199.250 (230)181.208.242.32 (128)190.8.164.26 (105)38.188.238.31 (103)View all →🏢 Same network: AS264778
View all →Security Intelligence
💡 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.
💡 Network Flow Analysis
Analyzing network flows (NetFlow, sFlow, IPFIX) provides visibility into traffic patterns without inspecting packet contents. Flow data reveals scanning activity, data exfiltration, lateral movement, and command-and-control channels at scale.