
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.89.128.213 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 |
| 21242 | Unknown | Low | Service on port 21242 |
| CVE ID | Link |
|---|---|
| CVE-2020-14058 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2020-11945 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2016-3947 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2019-18679 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2018-19132 | NVD → |
| CVE-2015-5400 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2016-4553 | NVD → |
| CVE-2021-28652 | NVD → |
🔴 This host has 56 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.89.128.213 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.89.128.213 originates from London, United Kingdom, operating on the network of XT GLOBAL NETWORKS LTD.. 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 30 malicious IPs originating from United Kingdom, positioning it as a notable contributor to global threat activity. A threat score of 70/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.
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.
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.
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.