IP Threat Report
170.205.27.241
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Burst: 6 req / 2s | 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 170.205.27.241 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
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 170.205.27.241.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 6379 | Redis | Critical | Redis in-memory database — frequently misconfigured without auth |
| 27017 | MongoDB | Critical | MongoDB — commonly found exposed without authentication |
⚠️ Network scanning reveals 2 dangerous services exposed on 170.205.27.241. Open database ports suggest possible data exfiltration risk. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2026-22795 | NVD → |
| CVE-2026-22796 | NVD → |
| CVE-2025-69421 | NVD → |
| CVE-2025-69419 | NVD → |
| CVE-2009-3767 | NVD → |
| CVE-2025-69418 | NVD → |
| CVE-2024-6119 | NVD → |
| CVE-2019-0190 | NVD → |
| CVE-2009-3766 | NVD → |
| CVE-2025-68160 | NVD → |
| CVE-2009-1390 | NVD → |
| CVE-2025-69420 | NVD → |
| CVE-2009-3765 | NVD → |
| CVE-2025-15467 | NVD → |
🔴 Security scanning identified 14 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
170.205.27.241 has been assigned a threat score of 95/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
📊 Threat Analysis
Our monitoring infrastructure has identified 170.205.27.241, geolocated to Sterling, United States, operating on the network of AME Hosting LLC, as a source of suspicious network activity. During its 3-day observation window, we recorded 6 hostile requests from this IP — roughly 2 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. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 104 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 95/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
💡 File Upload Vulnerabilities
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.
💡 BGP Hijacking and IP Spoofing
Border Gateway Protocol hijacking allows attackers to redirect internet traffic through their infrastructure. While less common than application-level attacks, BGP hijacks can intercept sensitive data, inject malware, or cause widespread service disruption.