
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| 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 163.44.192.46 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 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| CVE ID | Link |
|---|---|
| CVE-2025-1861 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2024-8925 | NVD → |
| CVE-2024-8926 | NVD → |
| CVE-2024-8927 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2024-8932 | NVD → |
| CVE-2025-1735 | NVD → |
| CVE-2024-3566 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2025-1736 | NVD → |
| CVE-2025-1220 | NVD → |
| CVE-2024-11234 | NVD → |
| CVE-2024-9026 | NVD → |
| CVE-2007-4723 | NVD → |
| CVE-2025-1219 | NVD → |
| CVE-2013-2220 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2025-1734 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2025-6491 | NVD → |
| CVE-2013-0941 | NVD → |
| CVE-2025-14178 | NVD → |
| CVE-2024-11233 | NVD → |
🔴 Security scanning identified 35 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.
163.44.192.46 has been assigned a threat score of 85/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:
Threat intelligence analysis has linked 163.44.192.46 to malicious activity originating from Hanoi, Vietnam, operating on the network of GMO-Z.com Runsystem Joint Stock Company. The address has been under observation since its initial detection. Over a period of 13 days, this IP generated 3 malicious requests, averaging approximately 0.2 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 101 flagged addresses, Vietnam represents a significant presence in our threat database. A threat score of 85/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.
Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.
Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.