
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.
Block scanning from 23.236.203.42: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
IP 23.236.203.42 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-45802 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2019-18678 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2019-12529 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2018-19132 | NVD → |
| CVE-2019-12519 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2016-10002 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2025-54574 | NVD → |
🔴 This host has 57 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.
23.236.203.42 has been assigned a threat score of 140/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 23.236.203.42, 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. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 177 flagged addresses, United States represents a significant presence in our threat database. 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.
XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.
Passive DNS databases record historical DNS resolution data, enabling analysts to track domain changes, identify related infrastructure, and discover malicious domains sharing hosting with known threats. This historical context is invaluable for threat investigation.