IP Threat Report
138.201.23.123
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 138.201.23.123 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 138.201.23.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 138.201.23.123 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
Neighbors in 138.201.23.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 |
|---|---|---|---|
| 53 | DNS | Low | DNS server — potential for DNS amplification attacks |
| 88 | Unknown | Low | Service on port 88 |
| 110 | POP3 | Low | Service on port 110 |
| 143 | IMAP | Low | Service on port 143 |
| 445 | SMB | Critical | SMB file sharing — high-risk for EternalBlue and ransomware |
| 993 | IMAPS | Low | Service on port 993 |
| 2082 | Unknown | Low | Service on port 2082 |
| 2087 | Unknown | Low | Service on port 2087 |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
| 4190 | Unknown | Low | Service on port 4190 |
⚠️ 2 high-risk ports detected on 138.201.23.123. 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-2020-0796 | NVD → |
🔴 Security scanning identified 1 vulnerability entries on this host. Even a small number of CVEs can represent significant risk. Consult NVD advisories for details.
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
138.201.23.123 has been assigned a threat score of 95/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
📊 Threat Analysis
IP address 138.201.23.123 has been traced to Falkenstein, Germany, operating on the network of Hetzner Online GmbH. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. 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. With 164 flagged addresses, Germany 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 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.
Related Threats
Security Intelligence
💡 HTTP Request Smuggling
Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.
💡 Network Segmentation Benefits
Proper network segmentation limits the blast radius of breaches. Even if attackers compromise one segment, properly configured network boundaries prevent lateral movement to critical systems, databases, and administrative interfaces.