IP Threat Report
163.52.135.4
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 10/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 11/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 12/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 13/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 14/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 15/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 19/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 20/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 21/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 22/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 23/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 24/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 26/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 27/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 5/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 6/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 7/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 8/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 9/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 12 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 13 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 14 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 16 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 17 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 18 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 19 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 21 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 22 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 24 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 27 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 9 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 10 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 15 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 16 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 19 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 20 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 21 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 7 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
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
We have detected 3 malicious IPs from this autonomous system.
Recommendations
Actions taken & recommended
- IP 163.52.135.4 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 163.52.135.0/24
- 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 163.52.135.4 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 163.52.135.4.
🤖 Bot Detection
Address UA spoofing from 163.52.135.4: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Neighbors in 163.52.135.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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
163.52.135.4 has been assigned a threat score of 340/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 163.52.135.4, geolocated to Madiun, Indonesia, operating on the network of CV Griya Cloud Server, as a source of suspicious network activity. Over a period of 15 days, this IP generated 9,279 malicious requests, averaging approximately 618.6 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 combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Our records show 1,091 malicious IPs originating from Indonesia, positioning it as a major contributor to global threat activity. At 340/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
🇮🇩 Top threats from Indonesia
157.15.40.62 (340)157.15.40.88 (340)157.15.40.89 (340)157.15.40.61 (340)157.15.40.93 (340)View all →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.
💡 VPN Exit Node Reputation
VPN exit nodes aggregate traffic from many users, creating mixed reputation profiles. While legitimate users seek privacy, attackers exploit VPN services to anonymize malicious activity, making IP-based blocking of VPN nodes a complex policy decision.