IP Threat Report
20.111.63.125
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 96 | Medium-risk: admin panels, config files | +60 | |
| Burst: 62 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 144 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Danger strong hits: 357 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 3376 | Medium-risk: admin panels, config files | +60 | |
| Burst: 33 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 100 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 45 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 395 | Medium-risk: admin panels, config files | +60 | |
| Burst: 31 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 93 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 20.111.63.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 20.111.63.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 Bot Detection
Address UA spoofing from 20.111.63.125: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Directory Scan Defense
IP 20.111.63.125 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Traffic Flood Defense
IP 20.111.63.125 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Neighbors in 20.111.63.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
20.111.63.125 has been assigned a threat score of 245/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 20.111.63.125, located in Paris, France, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 8 malicious requests, averaging approximately 8 requests per day. 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. France currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 245/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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
💡 User-Agent Analysis Techniques
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
💡 False Positive Management
False positives erode trust in security systems and waste analyst resources. Effective management requires feedback loops, allowlisting mechanisms, contextual analysis, and regular tuning of detection rules based on operational experience.