
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| 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.229.32.60: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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 |
| 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-2023-49288 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2019-12526 | NVD → |
| CVE-2019-12519 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2019-12523 | NVD → |
| CVE-2018-1000027 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2018-19132 | NVD → |
| CVE-2019-18860 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2020-15811 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2023-46847 | 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.229.32.60 has been assigned a threat score of 70/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
The following attack categories were identified:
Our monitoring infrastructure has identified 23.229.32.60, geolocated to Buffalo, United States, operating on the network of B2 Net Solutions Inc., as a source of suspicious network activity. Our sensors captured 2 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~2 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 183 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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.
RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.
Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.