IP Threat Report
1.179.199.2
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 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 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Imported from old blocklist | Behavioral anomaly detected by automated analysis | +0 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 12 | Medium-risk: admin panels, config files | +60 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 1.179.199.2 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Directory Scan Defense
IP 1.179.199.2 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🤖 Bot Detection
Address UA spoofing from 1.179.199.2: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Open Ports & Services
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 |
| 135 | Unknown | Low | Service on port 135 |
| 445 | SMB | Critical | SMB file sharing — high-risk for EternalBlue and ransomware |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
| 3389 | RDP | High | Remote Desktop Protocol — primary target for ransomware attacks |
| 5938 | Unknown | Low | Service on port 5938 |
| 5985 | Unknown | Low | Service on port 5985 |
⚠️ Network scanning reveals 3 dangerous services exposed on 1.179.199.2. 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-2022-28330 | NVD → |
| CVE-2009-3555 | NVD → |
| CVE-2018-1301 | NVD → |
| CVE-2007-6750 | NVD → |
| CVE-2009-0023 | NVD → |
| CVE-2016-8612 | NVD → |
| CVE-2013-0941 | NVD → |
| CVE-2010-0425 | NVD → |
| CVE-2009-1890 | NVD → |
| CVE-2021-39275 | NVD → |
| CVE-2009-1955 | NVD → |
| CVE-2009-1956 | NVD → |
| CVE-2022-28615 | NVD → |
| CVE-2015-0228 | NVD → |
| CVE-2013-5704 | NVD → |
| CVE-2016-4975 | NVD → |
| CVE-2011-3192 | NVD → |
| CVE-2021-32791 | NVD → |
| CVE-2012-0031 | NVD → |
| CVE-2022-22721 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2024-40898 | NVD → |
| CVE-2023-31122 | NVD → |
| CVE-2012-3499 | NVD → |
| CVE-2010-0408 | NVD → |
🔴 This host has 93 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.
Blacklist Status (DNSBL)
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.
Threat Analysis
1.179.199.2 has been assigned a threat score of 180/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 Analysis
Network traffic from 1.179.199.2, located in Khwaeng Thung Song Hong, Thailand, operating on the network of TOT Public Company Limited, has been classified as malicious by our automated threat scoring engine. Over a period of 70 days, this IP generated 37 malicious requests, averaging approximately 0.5 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 dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Thailand currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. At 180/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.
Related Threats
🇹🇭 Top threats from Thailand
8.213.218.53 (305)118.175.94.213 (268)98.159.43.111 (255)98.159.43.149 (255)98.159.43.117 (255)View all →🏢 Same network: AS131293
View all →Security Intelligence
💡 API Abuse and Enumeration
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.
💡 CORS Misconfiguration Exploitation
Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.