
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: 5 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.134 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 172.245.149.134 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 |
| 1344 | Unknown | Low | Service on port 1344 |
| 8000 | Unknown | Low | Service on port 8000 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 21242 | Unknown | Low | Service on port 21242 |
| 52951 | Unknown | Low | Service on port 52951 |
| CVE ID | Link |
|---|---|
| CVE-2019-12525 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2020-11945 | NVD → |
| CVE-2019-12526 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2016-10002 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2016-10003 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2019-18860 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2019-12528 | NVD → |
| CVE-2019-18678 | 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.134 has been assigned a threat score of 140/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:
Our monitoring infrastructure has identified 172.245.149.134, geolocated to Buffalo, United States, operating on the network of HostPapa, as a source of suspicious network activity. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 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. 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.
WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.
When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.