
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.
Block scanning from 189.198.239.110: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 53 | DNS | Low | DNS server — potential for DNS amplification attacks |
| 70 | Unknown | Low | Service on port 70 |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 2000 | Unknown | Low | Service on port 2000 |
| 3389 | RDP | High | Remote Desktop Protocol — primary target for ransomware attacks |
| 8000 | Unknown | Low | Service on port 8000 |
| 8993 | Unknown | Low | Service on port 8993 |
⚠️ 1 high-risk port detected on 189.198.239.110. Exposed RDP (3389) is the #1 entry point for ransomware attacks. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2026-34032 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2017-15710 | NVD → |
| CVE-2019-0217 | NVD → |
| CVE-2025-53020 | NVD → |
| CVE-2022-28615 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2025-65082 | NVD → |
| CVE-2020-13938 | NVD → |
| CVE-2020-1927 | NVD → |
| CVE-2022-22720 | NVD → |
| CVE-2026-33523 | NVD → |
| CVE-2019-0211 | NVD → |
| CVE-2026-33007 | NVD → |
| CVE-2021-34798 | NVD → |
| CVE-2017-15715 | NVD → |
| CVE-2021-26691 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2018-1283 | NVD → |
| CVE-2021-40438 | NVD → |
| CVE-2024-24795 | NVD → |
| CVE-2020-9490 | NVD → |
| CVE-2026-33006 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2019-0196 | NVD → |
🔴 This host has 101 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.
189.198.239.110 has been assigned a threat score of 83/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
Network traffic from 189.198.239.110, located in Guaymas, Mexico, operating on the network of Mega Cable, S.A. de C.V., has been classified as malicious by our automated threat scoring engine. The address has been active for 1 days in our monitoring system, producing 4 flagged requests at a rate of ~4/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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 122 flagged addresses, Mexico represents a significant presence in our threat database. 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.
SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.
Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.