
ABUSE.MOM — BEHAVE OR GET EXPOSED
| 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 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 107.173.136.139 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 107.173.136.139.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 1344 | Unknown | Low | Service on port 1344 |
| 3128 | Unknown | Low | Service on port 3128 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 21242 | Unknown | Low | Service on port 21242 |
| CVE ID | Link |
|---|---|
| CVE-2025-62168 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2019-18679 | NVD → |
| CVE-2019-12523 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2019-18860 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2016-10003 | NVD → |
| CVE-2019-18678 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2019-12522 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2019-12519 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2024-45802 | NVD → |
🔴 This host has 59 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.
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.
107.173.136.139 has been assigned a threat score of 140/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:
Network traffic from 107.173.136.139, located in Buffalo, United States, operating on the network of HostPapa, has been classified as malicious by our automated threat scoring engine. Over a period of 9 days, this IP generated 3 malicious requests, averaging approximately 0.3 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 dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 203 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 140/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.
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.
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.