IP Threat Report
139.59.90.174
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| 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 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 14 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
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 139.59.90.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 139.59.90.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 User-Agent Anomaly Defense
IP 139.59.90.174 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🔎 Path Enumeration Protection
Block scanning from 139.59.90.174: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 139.59.90.174 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Neighbors in 139.59.90.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 |
| 82 | Unknown | Low | Service on port 82 |
| 84 | Unknown | Low | Service on port 84 |
| 111 | Unknown | Low | Service on port 111 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 5060 | Unknown | Low | Service on port 5060 |
| 5222 | Unknown | Low | Service on port 5222 |
| 8001 | Unknown | Low | Service on port 8001 |
| 8089 | Unknown | Low | Service on port 8089 |
| CVE ID | Link |
|---|---|
| CVE-2021-32791 | NVD → |
| CVE-2021-26691 | NVD → |
| CVE-2018-1302 | NVD → |
| CVE-2018-0732 | NVD → |
| CVE-2023-3817 | NVD → |
| CVE-2024-38472 | NVD → |
| CVE-2013-5704 | NVD → |
| CVE-2022-1292 | NVD → |
| CVE-2016-2161 | NVD → |
| CVE-2023-0215 | NVD → |
| CVE-2023-2650 | NVD → |
| CVE-2013-4352 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2022-31628 | NVD → |
| CVE-2023-25690 | NVD → |
| CVE-2009-3766 | NVD → |
| CVE-2024-38475 | NVD → |
| CVE-2019-10092 | NVD → |
| CVE-2019-1559 | NVD → |
| CVE-2020-1927 | NVD → |
| CVE-2023-0286 | NVD → |
| CVE-2021-21708 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2022-22720 | NVD → |
| CVE-2018-1312 | NVD → |
🔴 This host has 163 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
139.59.90.174 has been assigned a threat score of 180/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 139.59.90.174, located in Bengaluru, India, operating on the network of DIGITALOCEAN, has been classified as malicious by our automated threat scoring engine. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Our records show 111 malicious IPs originating from India, positioning it as a significant contributor to global threat activity. With a threat score of 180/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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
💡 TLS Fingerprinting (JA3/JA4)
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.
💡 HTTP Header Analysis for Threat Detection
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.