
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| 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 | |
| UA bot: python | Known bot/crawler User-Agent detected | +40 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 178.128.110.54 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
IP 178.128.110.54 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 |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 1433 | MSSQL | High | Service on port 1433 |
| 10000 | Unknown | Low | Service on port 10000 |
| CVE ID | Link |
|---|---|
| CVE-2023-38709 | NVD → |
| CVE-2024-27316 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2025-65082 | NVD → |
| CVE-2024-43394 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2024-24795 | NVD → |
| CVE-2025-49812 | NVD → |
| CVE-2024-40898 | NVD → |
| CVE-2023-27522 | NVD → |
| CVE-2025-66200 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2024-38475 | NVD → |
| CVE-2024-39573 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2024-38477 | NVD → |
| CVE-2024-42516 | NVD → |
| CVE-2025-55753 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2024-43204 | NVD → |
| CVE-2023-25690 | NVD → |
| CVE-2023-31122 | NVD → |
| CVE-2025-23048 | NVD → |
| CVE-2024-38472 | NVD → |
🔴 Security scanning identified 43 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
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.
178.128.110.54 has been assigned a threat score of 120/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
Threat intelligence analysis has linked 178.128.110.54 to malicious activity originating from Singapore, Singapore, operating on the network of DigitalOcean, LLC. The address has been under observation since its initial detection. Over a period of 4 days, this IP generated 4 malicious requests, averaging approximately 1 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. With 140 flagged addresses, Singapore represents a significant presence in our threat database. At 120/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
Modern phishing operations use sophisticated infrastructure including lookalike domains, valid TLS certificates, and evasion techniques like cloaking and geofencing. Analyzing this infrastructure reveals campaigns before they reach their targets.