
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| POST requests present | Behavioral anomaly detected by automated analysis | +8 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 197.254.238.254 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 53 | DNS | Low | DNS server — potential for DNS amplification attacks |
| 123 | Unknown | Low | Service on port 123 |
| 161 | Unknown | Low | Service on port 161 |
| 1701 | Unknown | Low | Service on port 1701 |
| 3128 | Unknown | Low | Service on port 3128 |
| CVE ID | Link |
|---|---|
| CVE-2016-6515 | NVD → |
| CVE-2020-14145 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2018-19052 | NVD → |
| CVE-2016-8858 | NVD → |
| CVE-2016-3115 | NVD → |
| CVE-2019-11072 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2016-6210 | NVD → |
| CVE-2016-10708 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2016-0778 | NVD → |
| CVE-2016-10009 | NVD → |
| CVE-2016-1908 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2018-15473 | NVD → |
| CVE-2018-20685 | NVD → |
| CVE-2016-10012 | NVD → |
| CVE-2016-0777 | NVD → |
| CVE-2015-8325 | NVD → |
| CVE-2016-10011 | NVD → |
| CVE-2023-48795 | NVD → |
🔴 This host has 35 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.
197.254.238.254 has been assigned a threat score of 68/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:
197.254.238.254 is registered in Khartoum, SD, operating on the network of Kanar Telecommunication (Canar Telecom Co.Ltd). This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 12 malicious IPs originating from SD, positioning it as a notable contributor to global threat activity. At 68/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
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.
Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.
Cache poisoning manipulates web cache behavior to serve malicious content to other users. By identifying unkeyed inputs that influence cached responses, attackers can inject JavaScript, redirect users, or cause denial of service at scale through the cache infrastructure.