IP Threat Report
20.104.97.84
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: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 292 | Medium-risk: admin panels, config files | +60 | |
| Burst: 23 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 84 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 71 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 24 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 86 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 289 | Medium-risk: admin panels, config files | +60 | |
| Burst: 76 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 81 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 438 | Medium-risk: admin panels, config files | +60 | |
| Burst: 83 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 436 | Medium-risk: admin panels, config files | +60 | |
| Burst: 74 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 88 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 244 | Medium-risk: admin panels, config files | +60 | |
| Burst: 85 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 366 | Medium-risk: admin panels, config files | +60 | |
| Burst: 22 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 72 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 78 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 80 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 75 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 21 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 79 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 73 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 374 | Medium-risk: admin panels, config files | +60 | |
| Burst: 18 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 62 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.104.97.84 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.104.97.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.104.97.84: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.104.97.84.
🔎 Path Enumeration Protection
Block scanning from 20.104.97.84: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Neighbors in 20.104.97.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.104.97.84 has been assigned a threat score of 280/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
20.104.97.84 is registered in Toronto, Canada, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 8 days in our monitoring system, producing 29 flagged requests at a rate of ~3.6/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. With 102 flagged addresses, Canada 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
💡 TLS Fingerprinting (JA3/JA4)
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
💡 XML External Entity (XXE) Attacks
XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.