
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| 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 192.186.163.44 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 192.186.163.44 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 3128 | Unknown | Low | Service on port 3128 |
| 8000 | Unknown | Low | Service on port 8000 |
| 8800 | Unknown | Low | Service on port 8800 |
| CVE ID | Link |
|---|---|
| CVE-2020-11945 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2014-3609 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2016-4051 | NVD → |
| CVE-2016-4053 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2018-1000027 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2018-19131 | NVD → |
| CVE-2019-12528 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2019-18678 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2016-4052 | NVD → |
| CVE-2015-5400 | NVD → |
| CVE-2019-12529 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2019-12524 | NVD → |
🔴 This host has 77 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.
192.186.163.44 has been assigned a threat score of 120/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:
Network traffic from 192.186.163.44, located in Buffalo, United States, operating on the network of B2 Net Solutions Inc., has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per 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. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 185 blocked IPs in our database, making it a significant source of malicious traffic. A score of 120/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.
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.
WebSocket connections bypass traditional HTTP security controls, creating opportunities for cross-site WebSocket hijacking, denial of service, and data injection. Proper origin validation, authentication, and message rate limiting are essential for secure WebSocket implementations.