IP Threat Report
185.244.104.205
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Burst: 9 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 185.244.104.205 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
🤖 User-Agent Anomaly Defense
IP 185.244.104.205 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🌊 Traffic Flood Defense
IP 185.244.104.205 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 |
|---|---|---|---|
| 111 | Unknown | Low | Service on port 111 |
| 1024 | Unknown | Low | Service on port 1024 |
| 1080 | Unknown | Low | Service on port 1080 |
| 1181 | Unknown | Low | Service on port 1181 |
| 1200 | Unknown | Low | Service on port 1200 |
| 1234 | Unknown | Low | Service on port 1234 |
| 1292 | Unknown | Low | Service on port 1292 |
| 1337 | Unknown | Low | Service on port 1337 |
| 1370 | Unknown | Low | Service on port 1370 |
| 1400 | Unknown | Low | Service on port 1400 |
| 1414 | Unknown | Low | Service on port 1414 |
| 1433 | MSSQL | High | Service on port 1433 |
| 1443 | Unknown | Low | Service on port 1443 |
| 1457 | Unknown | Low | Service on port 1457 |
| 1459 | Unknown | Low | Service on port 1459 |
| 1471 | Unknown | Low | Service on port 1471 |
| 1521 | Unknown | Low | Service on port 1521 |
| 1599 | Unknown | Low | Service on port 1599 |
| 1800 | Unknown | Low | Service on port 1800 |
| 1801 | Unknown | Low | Service on port 1801 |
| 1883 | Unknown | Low | Service on port 1883 |
| 1911 | Unknown | Low | Service on port 1911 |
| 1925 | Unknown | Low | Service on port 1925 |
| 1953 | Unknown | Low | Service on port 1953 |
| 1958 | Unknown | Low | Service on port 1958 |
| 1969 | Unknown | Low | Service on port 1969 |
| 1971 | Unknown | Low | Service on port 1971 |
| 3128 | Unknown | Low | Service on port 3128 |
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.244.104.205 has been assigned a threat score of 110/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
Network traffic from 185.244.104.205, located in Frankfurt, Germany, operating on the network of Ferdinand Zink trading as Tube-Hosting, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. 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 dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 101 flagged addresses, Germany represents a significant presence in our threat database. A score of 110/100 places this address in the top tier of severity. Block and investigate any historical connections.
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 Germany
15.220.152.241 (320)77.81.65.244 (313)185.168.29.98 (313)91.217.249.222 (305)212.30.36.219 (305)View all →🏢 Same network: AS213200
View all →Security Intelligence
💡 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.
💡 Critical Infrastructure Targeting
Attacks on power grids, water systems, and transportation networks have moved from theoretical to practical threats. Industrial control systems often lack modern security features, making them vulnerable to both targeted and opportunistic attacks.