IP Threat Report
185.213.174.125
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 strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 37 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 37 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger strong hits: 27 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 58 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 58 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 38 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 38 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 21 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 21 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 185.213.174.125 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 185.213.174.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 185.213.174.125 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🔎 Path Enumeration Protection
Block scanning from 185.213.174.125: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 185.213.174.125 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Neighbors in 185.213.174.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 |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
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.213.174.125 has been assigned a threat score of 230/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 185.213.174.125, located in Dronten, Netherlands, operating on the network of NextGenWebs, has been classified as malicious by our automated threat scoring engine. Our sensors captured 9 malicious requests from this address across a 8-day span, reflecting a sustained attack cadence of ~1.1 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Netherlands currently accounts for 168 blocked IPs in our database, making it a significant source of malicious traffic. At 230/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 Netherlands
185.184.192.251 (338)45.88.138.44 (320)45.82.64.236 (315)5.181.169.192 (313)157.22.73.141 (313)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.
💡 Digital Forensics Fundamentals
Digital forensics preserves and analyzes electronic evidence following attacks. Proper chain of custody, forensic imaging, timeline reconstruction, and artifact analysis are essential for understanding attack scope, attribution, and preventing recurrence.