IP Threat Report
18.218.45.95
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 19 | Medium-risk: admin panels, config files | +60 | |
| Burst: 18 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 21 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 16 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 9 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 17 req / 10s | 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 18.218.45.95 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
🌊 Traffic Flood Defense
IP 18.218.45.95 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 |
|---|---|---|---|
| 17 | Unknown | Low | Service on port 17 |
| 19 | Unknown | Low | Service on port 19 |
| 21 | FTP | Medium | File Transfer Protocol — often targeted for anonymous login attacks |
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 2087 | Unknown | Low | Service on port 2087 |
| 2345 | Unknown | Low | Service on port 2345 |
| 4085 | Unknown | Low | Service on port 4085 |
| 5009 | Unknown | Low | Service on port 5009 |
| 6700 | Unknown | Low | Service on port 6700 |
| 7779 | Unknown | Low | Service on port 7779 |
| 8033 | Unknown | Low | Service on port 8033 |
| 8188 | Unknown | Low | Service on port 8188 |
| 8649 | Unknown | Low | Service on port 8649 |
| 8728 | Unknown | Low | Service on port 8728 |
| 8818 | Unknown | Low | Service on port 8818 |
| 8834 | Unknown | Low | Service on port 8834 |
| 12001 | Unknown | Low | Service on port 12001 |
| 12303 | Unknown | Low | Service on port 12303 |
| 12577 | Unknown | Low | Service on port 12577 |
| 15001 | Unknown | Low | Service on port 15001 |
| 16010 | Unknown | Low | Service on port 16010 |
| 20040 | Unknown | Low | Service on port 20040 |
| 30002 | Unknown | Low | Service on port 30002 |
| 44500 | Unknown | Low | Service on port 44500 |
⚠️ 1 high-risk port detected on 18.218.45.95. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2015-0228 | NVD → |
| CVE-2024-27316 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2009-3767 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2025-12781 | NVD → |
| CVE-2011-4317 | NVD → |
| CVE-2007-5000 | NVD → |
| CVE-2023-27043 | NVD → |
| CVE-2016-0704 | NVD → |
| CVE-2022-48564 | NVD → |
| CVE-2024-9287 | NVD → |
| CVE-2019-10160 | NVD → |
| CVE-2014-0076 | NVD → |
| CVE-2017-18207 | NVD → |
| CVE-2024-0727 | NVD → |
| CVE-2020-7041 | NVD → |
| CVE-2007-6750 | NVD → |
| CVE-2022-28330 | NVD → |
| CVE-2021-44790 | NVD → |
| CVE-2009-3720 | NVD → |
| CVE-2008-7270 | NVD → |
| CVE-2003-0020 | NVD → |
| CVE-2025-69419 | NVD → |
| CVE-2022-48566 | NVD → |
🔴 Security scanning identified 255 vulnerability entries on this host. This volume strongly suggests severely outdated software. 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
18.218.45.95 has been assigned a threat score of 155/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
Our monitoring infrastructure has identified 18.218.45.95, geolocated to Dublin, United States, operating on the network of Amazon.com, Inc., as a source of suspicious network activity. Our sensors captured 3 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~3 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. Our records show 130 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 155/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
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →Security Intelligence
💡 Directory Traversal Attacks
Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.
💡 Data Breach Impact Assessment
The impact of data breaches extends beyond immediate financial losses. Regulatory fines, legal liability, reputational damage, and customer churn create long-term costs that often exceed the direct costs of incident response and remediation.