
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.
IP 152.232.47.100 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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 |
| 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-2025-62168 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2019-18679 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2019-12525 | NVD → |
| CVE-2019-12529 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2019-12523 | NVD → |
| CVE-2019-12521 | NVD → |
🔴 This host has 59 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.
152.232.47.100 has been assigned a threat score of 70/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.
The following attack categories were identified:
The address 152.232.47.100 originates from Los Angeles, United States, operating on the network of HostPapa. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 202 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 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.
XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.
The impact of data breaches extends beyond immediate financial losses. Regulatory fines, legal liability, reputational damage, and customer churn create long-term costs that often exceed the direct costs of incident response and remediation.