
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 23.236.163.231 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 23.236.163.231 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 |
|---|---|---|---|
| 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 |
| 8800 | Unknown | Low | Service on port 8800 |
| CVE ID | Link |
|---|---|
| CVE-2024-37894 | NVD → |
| CVE-2019-12526 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2016-10002 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2019-12522 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2020-11945 | NVD → |
| CVE-2019-12525 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2019-18679 | NVD → |
| CVE-2019-18860 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2018-19132 | NVD → |
🔴 Security scanning identified 56 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.
23.236.163.231 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:
Threat intelligence analysis has linked 23.236.163.231 to malicious activity originating from Buffalo, United States, operating on the network of B2 Net Solutions Inc.. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 177 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 belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.
Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.
Immutable, offline backups remain the most effective defense against ransomware. The 3-2-1 rule — three copies on two media types with one offsite — combined with regular recovery testing ensures business continuity after encryption attacks.