IP Threat Report
135.225.75.187
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 117/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 119/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 134/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 148/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 152/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 159/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 162/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 165/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 175/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 185/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 188/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 193/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 194/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 38/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 49/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 51/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 53/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 54/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 56/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 58/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 62/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 63/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 64/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 69/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 133 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 262 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 266 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 267 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 306 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 320 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 334 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 399 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 480 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 513 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 140 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 187 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 5 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 73 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 94 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
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 135.225.75.187 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
🔎 Directory Scan Defense
IP 135.225.75.187 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Traffic Flood Defense
IP 135.225.75.187 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
🤖 User-Agent Anomaly Defense
IP 135.225.75.187 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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
135.225.75.187 has been assigned a threat score of 280/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
Threat intelligence analysis has linked 135.225.75.187 to malicious activity originating from Gävle, Sweden, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. During its 7-day observation window, we recorded 2,059 hostile requests from this IP — roughly 294.1 per day on average. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. With 101 flagged addresses, Sweden represents a significant presence in our threat database. At 280/100, this is an extremely high-risk address. All traffic should be considered hostile.
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
Security Intelligence
💡 DDoS Mitigation Approaches
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
💡 SSH Brute Force Defense
SSH servers face constant brute force attacks targeting common usernames and weak passwords. Key-based authentication, fail2ban, non-standard ports, and IP allowlisting dramatically reduce the attack surface. Monitoring auth logs reveals active campaigns and compromised credentials.