
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 172.245.149.225 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 172.245.149.225.
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 |
| 8000 | Unknown | Low | Service on port 8000 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 52931 | Unknown | Low | Service on port 52931 |
| CVE ID | Link |
|---|---|
| CVE-2016-10003 | NVD → |
| CVE-2020-15811 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2019-12525 | NVD → |
| CVE-2019-12519 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2018-19132 | NVD → |
| CVE-2019-12528 | NVD → |
| CVE-2019-18860 | NVD → |
| CVE-2024-37894 | 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.
172.245.149.225 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:
Our monitoring infrastructure has identified 172.245.149.225, geolocated to Buffalo, United States, operating on the network of HostPapa, as a source of suspicious network activity. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 199 blocked IPs in our database, making it a significant source of malicious traffic. At 140/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.
Watering hole attacks compromise websites frequently visited by target organizations. Rather than attacking targets directly, adversaries infect trusted resources, exploiting the inherent trust users place in regularly visited sites.