IP Threat Report
192.110.166.16
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 |
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 192.110.166.16 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 192.110.166.16: 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 |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 53 | DNS | Low | DNS server — potential for DNS amplification attacks |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8888 | HTTP-Alt | Low | Service on port 8888 |
| CVE ID | Link |
|---|---|
| CVE-2018-1000027 | NVD → |
| CVE-2017-9788 | NVD → |
| CVE-2023-31122 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2015-3455 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2022-29404 | NVD → |
| CVE-2014-6270 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2014-7141 | NVD → |
| CVE-2015-3185 | NVD → |
| CVE-2017-3167 | NVD → |
| CVE-2021-32792 | NVD → |
| CVE-2014-3581 | NVD → |
| CVE-2014-0118 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2019-10098 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-32786 | NVD → |
| CVE-2019-12529 | NVD → |
| CVE-2016-4554 | NVD → |
| CVE-2020-13938 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2017-7679 | NVD → |
| CVE-2022-22721 | NVD → |
🔴 This host has 174 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
192.110.166.16 has been assigned a threat score of 85/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
📊 Threat Analysis
192.110.166.16 is registered in Phoenix, United States, operating on the network of Input Output Flood LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 106 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 85/100, this IP warrants immediate defensive action.
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 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
💡 Server-Side Request Forgery (SSRF)
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.
💡 IoT Device Compromise Patterns
Internet of Things devices are prime targets for botnet recruitment due to weak default credentials, infrequent updates, and always-on connectivity. Compromised IoT devices generate persistent scanning and attack traffic without their owners knowledge.