IP Threat Report
20.100.177.179
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: 70 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 546 | Medium-risk: admin panels, config files | +60 | |
| Burst: 42 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 145 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 364 | 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: 43 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 141 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 366 | Medium-risk: admin panels, config files | +60 | |
| Burst: 53 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 180 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 41 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 133 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 45 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 153 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 54 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 518 | Medium-risk: admin panels, config files | +60 | |
| Burst: 152 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 368 | Medium-risk: admin panels, config files | +60 | |
| Burst: 50 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 163 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 40 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 137 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 200 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 56 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 178 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 400 | Medium-risk: admin panels, config files | +60 | |
| Burst: 54 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 176 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 569 | Medium-risk: admin panels, config files | +60 | |
| Burst: 193 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 65 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 200 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 603 | Medium-risk: admin panels, config files | +60 | |
| Burst: 165 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 402 | Medium-risk: admin panels, config files | +60 | |
| Burst: 58 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 74 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 64 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 55 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 404 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 19 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 202 | Medium-risk: admin panels, config files | +60 | |
| Burst: 62 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 184 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 51 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 197 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 190 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 392 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 398 | Medium-risk: admin panels, config files | +60 | |
| Burst: 47 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 140 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 597 | Medium-risk: admin panels, config files | +60 | |
| Burst: 49 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 170 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 596 | 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 | |
| Burst: 66 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 143 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 174 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 57 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 191 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 52 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 63 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 181 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 38 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 130 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 161 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 138 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 60 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 150 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 195 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 198 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 352 | Medium-risk: admin panels, config files | +60 | |
| Burst: 187 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 43 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 37 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 117 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 58 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 528 | Medium-risk: admin panels, config files | +60 | |
| Burst: 136 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.177.179 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
🤖 User-Agent Anomaly Defense
IP 20.100.177.179 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.100.177.179.
🔎 Path Enumeration Protection
Block scanning from 20.100.177.179: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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.177.179 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
Threat intelligence analysis has linked 20.100.177.179 to malicious activity originating from Lorenskog, Norway, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Our sensors captured 59 malicious requests from this address across a 18-day span, reflecting a sustained attack cadence of ~3.3 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 101 flagged addresses, Norway 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
💡 HTTP Header Analysis for Threat Detection
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
💡 Command Injection Techniques
Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.