IP Threat Report
173.244.42.174
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 |
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 173.244.42.174 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 173.244.42.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
⚙️ Defensive Recommendations
Block 173.244.42.174 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
Neighbors in 173.244.42.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 1337 | Unknown | Low | Service on port 1337 |
| 6443 | Unknown | Low | Service on port 6443 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8081 | Unknown | Low | Service on port 8081 |
| 8443 | HTTPS-Alt | Low | Service on port 8443 |
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
173.244.42.174 has been assigned a threat score of 95/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
📊 Threat Analysis
Threat intelligence analysis has linked 173.244.42.174 to malicious activity originating from Seoul, South Korea, operating on the network of LogicWeb Inc.. The address has been under observation since its initial detection. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. The address operates as a VPN/proxy exit node. Attackers route traffic through anonymizing services to obscure their real location and evade IP-based security controls. With 106 flagged addresses, South Korea represents a significant presence in our threat database. At 95/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.
Related Threats
🇰🇷 Top threats from South Korea
4.217.180.34 (280)20.214.155.242 (280)20.214.157.214 (280)52.231.66.246 (280)20.194.25.241 (280)View all →Security Intelligence
💡 Remote Code Execution (RCE)
RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.
💡 Botnet Command and Control Evolution
Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.