IP Threat Report
111.125.83.172
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 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| POST requests present | Behavioral anomaly detected by automated analysis | +8 |
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 111.125.83.172 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 111.125.83.172: 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 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| CVE ID | Link |
|---|---|
| CVE-2019-16905 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2026-35414 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2020-14145 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2008-3844 | NVD → |
🔴 Security scanning identified 15 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
111.125.83.172 has been assigned a threat score of 83/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
📊 Threat Analysis
Our monitoring infrastructure has identified 111.125.83.172, geolocated to Iloilo City, Philippines, operating on the network of University of the Philippines Visayas, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 2 flagged requests at a rate of ~2/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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 101 malicious IPs originating from Philippines, positioning it as a significant contributor to global threat activity. The score of 83/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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 Philippines
194.61.41.46 (255)103.250.62.24 (213)180.191.168.156 (208)136.158.57.53 (208)136.158.82.180 (208)View all →🏢 Same network: AS132792
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.
💡 Threat Score Calculation Methods
Threat scoring combines multiple signals — request patterns, known signatures, IP reputation, geographic risk, and behavioral analysis — into a single actionable metric. Weighted scoring models allow tuning sensitivity to balance security with usability.