
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 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 41.90.122.183 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 |
|---|---|---|---|
| 65 | Unknown | Low | Service on port 65 |
| 90 | Unknown | Low | Service on port 90 |
| 104 | Unknown | Low | Service on port 104 |
| 135 | Unknown | Low | Service on port 135 |
| 137 | Unknown | Low | Service on port 137 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 445 | SMB | Critical | SMB file sharing — high-risk for EternalBlue and ransomware |
| 1434 | Unknown | Low | Service on port 1434 |
| 3389 | RDP | High | Remote Desktop Protocol — primary target for ransomware attacks |
| 5985 | Unknown | Low | Service on port 5985 |
| 9998 | Unknown | Low | Service on port 9998 |
| 51058 | Unknown | Low | Service on port 51058 |
⚠️ 2 high-risk ports detected on 41.90.122.183. Exposed RDP (3389) is the #1 entry point for ransomware attacks. SMB (445) exposure is associated with worm propagation and EternalBlue exploits. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2020-0796 | NVD → |
🔴 This host has 1 known CVE associated with its exposed services. Even a small number of CVEs can represent significant risk. 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.
41.90.122.183 has been assigned a threat score of 83/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
Network traffic from 41.90.122.183, located in Nairobi, KE, operating on the network of Safaricom Limited, has been classified as malicious by our automated threat scoring engine. 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. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. KE currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. A threat score of 83/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.
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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.