IP Threat Report
185.18.59.118
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 30 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 30 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 12 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 18 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 18 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Imported from old blocklist | Behavioral anomaly detected by automated analysis | +0 | |
| Burst: 28 req / 2s | Abnormally fast request rate — automated scanning | +35 |
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 185.18.59.118 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
🔎 Path Enumeration Protection
Block scanning from 185.18.59.118: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 185.18.59.118 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 21 | FTP | Medium | File Transfer Protocol — often targeted for anonymous login attacks |
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 25 | SMTP | Medium | SMTP mail server — can be abused for spam relay |
| 53 | DNS | Low | DNS server — potential for DNS amplification attacks |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 110 | POP3 | Low | Service on port 110 |
| 143 | IMAP | Low | Service on port 143 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 465 | Unknown | Low | Service on port 465 |
| 587 | Unknown | Low | Service on port 587 |
| 993 | IMAPS | Low | Service on port 993 |
| 995 | POP3S | Low | Service on port 995 |
⚠️ 1 high-risk port detected on 185.18.59.118. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2016-5094 | NVD → |
| CVE-2014-9652 | NVD → |
| CVE-2019-9638 | NVD → |
| CVE-2019-6110 | NVD → |
| CVE-2014-4698 | NVD → |
| CVE-2017-8923 | NVD → |
| CVE-2013-7456 | NVD → |
| CVE-2013-2220 | NVD → |
| CVE-2014-9705 | NVD → |
| CVE-2014-3587 | NVD → |
| CVE-2021-32792 | NVD → |
| CVE-2014-3581 | NVD → |
| CVE-2018-17082 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2022-31628 | NVD → |
| CVE-2015-3412 | NVD → |
| CVE-2017-9224 | NVD → |
| CVE-2022-22721 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2019-6977 | NVD → |
| CVE-2016-9934 | NVD → |
| CVE-2016-4343 | NVD → |
| CVE-2014-3597 | NVD → |
| CVE-2016-7132 | NVD → |
| CVE-2015-3411 | NVD → |
🔴 This host has 394 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
185.18.59.118 has been assigned a threat score of 195/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
The address 185.18.59.118 originates from Varna, Bulgaria, operating on the network of DigiCom.BG. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 10 days in our monitoring system, producing 33 flagged requests at a rate of ~3.3/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 Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 57 malicious IPs originating from Bulgaria, positioning it as a notable contributor to global threat activity. At 195/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 Bulgaria
85.11.167.90 (293)104.28.246.54 (280)85.11.167.15 (240)146.70.245.66 (230)85.11.167.80 (225)View all →🏢 Same network: AS34524
View all →Security Intelligence
💡 Credential Stuffing at Scale
Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.
💡 GraphQL Security Risks
GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.