IP Threat Report
20.24.203.130
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 | |
| Burst 13/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 14/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 49/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 50/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 114 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 122 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 124 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 171 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 64 | Medium-risk: admin panels, config files | +60 | |
| 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: 8 | 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 20.24.203.130 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 20.24.203.130 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 20.24.203.130.
🤖 User-Agent Anomaly Defense
IP 20.24.203.130 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
20.24.203.130 has been assigned a threat score of 280/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
📊 Threat Analysis
The address 20.24.203.130 originates from Hong Kong, Hong Kong, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 6-day observation window, we recorded 2,583 hostile requests from this IP — roughly 430.5 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 102 flagged addresses, Hong Kong represents a significant presence in our threat database. A score of 280/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
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.
💡 GeoIP Blocking Considerations
Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.