
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 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Block scanning from 107.172.85.23: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
IP 107.172.85.23 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
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 |
| 3128 | Unknown | Low | Service on port 3128 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8800 | Unknown | Low | Service on port 8800 |
| 21242 | Unknown | Low | Service on port 21242 |
| 52951 | Unknown | Low | Service on port 52951 |
| CVE ID | Link |
|---|---|
| CVE-2026-33515 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2018-19131 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2019-12522 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2020-11945 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2019-12519 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2019-12523 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2016-10003 | NVD → |
| CVE-2016-10002 | NVD → |
| CVE-2018-1000027 | NVD → |
| CVE-2025-59362 | NVD → |
🔴 Security scanning identified 59 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.
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.172.85.23 has been assigned a threat score of 140/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
Threat intelligence analysis has linked 107.172.85.23 to malicious activity originating from Buffalo, United States, operating on the network of HostPapa. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 2 flagged requests at a rate of ~2/day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 199 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 140/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
HTTP security headers provide defense-in-depth with minimal implementation effort. Key headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy, each addressing specific attack vectors.