IP Threat Report
20.100.197.204
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: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 238 | Medium-risk: admin panels, config files | +60 | |
| 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: 29 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 94 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 64 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 542 | Medium-risk: admin panels, config files | +60 | |
| Burst: 46 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 148 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 126 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 815 | Medium-risk: admin panels, config files | +60 | |
| Burst: 49 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 167 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 71 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 358 | Medium-risk: admin panels, config files | +60 | |
| Burst: 36 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 122 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 51 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 161 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 53 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 239 | Medium-risk: admin panels, config files | +60 | |
| Burst: 35 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 110 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 38 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 131 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 367 | Medium-risk: admin panels, config files | +60 | |
| Burst: 34 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 117 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 47 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 152 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 50 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 245 | Medium-risk: admin panels, config files | +60 | |
| Burst: 115 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 348 | Medium-risk: admin panels, config files | +60 | |
| Burst: 60 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 200 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 69 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 63 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 61 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 62 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 374 | Medium-risk: admin panels, config files | +60 | |
| Burst: 48 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 157 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 55 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 185 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.100.197.204 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.100.197.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.100.197.204: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Path Enumeration Protection
Block scanning from 20.100.197.204: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 20.100.197.204 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Neighbors in 20.100.197.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
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.100.197.204 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
20.100.197.204 is registered in Lorenskog, Norway, 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 6 days in our monitoring system, producing 20 flagged requests at a rate of ~3.3/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 101 malicious IPs originating from Norway, positioning it as a significant contributor to global threat activity. 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
💡 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.
💡 GDPR and Threat Intelligence
Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.