Dashboard›🇳🇴 Norway›20.100.172.153
ABUSE.MOM
THREAT REPORT

IP Threat Report
20.100.172.153

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-10 01:51:48
First seen: 2026-08-03 17:40:00
Last seen: 2026-08-16 01:04:37
280

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 280/100. Total malicious requests observed: 6538.

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
20.100.172.153
Type
Hosting
Country
🇳🇴 Norway
City
Lorenskog
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (norwaye)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
6538
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 100/10sAbnormally fast request rate — automated scanning+35
Burst 104/10sAbnormally fast request rate — automated scanning+35
Burst 108/10sAbnormally fast request rate — automated scanning+35
Burst 109/10sAbnormally fast request rate — automated scanning+35
Burst 110/10sAbnormally fast request rate — automated scanning+35
Burst 111/10sAbnormally fast request rate — automated scanning+35
Burst 112/10sAbnormally fast request rate — automated scanning+35
Burst 114/10sAbnormally fast request rate — automated scanning+35
Burst 117/10sAbnormally fast request rate — automated scanning+35
Burst 119/10sAbnormally fast request rate — automated scanning+35
Burst 123/10sAbnormally fast request rate — automated scanning+35
Burst 126/10sAbnormally fast request rate — automated scanning+35
Burst 127/10sAbnormally fast request rate — automated scanning+35
Burst 135/10sAbnormally fast request rate — automated scanning+35
Burst 139/10sAbnormally fast request rate — automated scanning+35
Burst 144/10sAbnormally fast request rate — automated scanning+35
Burst 153/10sAbnormally fast request rate — automated scanning+35
Burst 155/10sAbnormally fast request rate — automated scanning+35
Burst 162/10sAbnormally fast request rate — automated scanning+35
Burst 167/10sAbnormally fast request rate — automated scanning+35
Burst 175/10sAbnormally fast request rate — automated scanning+35
Burst 176/10sAbnormally fast request rate — automated scanning+35
Burst 179/10sAbnormally fast request rate — automated scanning+35
Burst 180/10sAbnormally fast request rate — automated scanning+35
Burst 190/10sAbnormally fast request rate — automated scanning+35
Burst 196/10sAbnormally fast request rate — automated scanning+35
Burst 200/10sAbnormally fast request rate — automated scanning+35
Burst 27/2sAbnormally fast request rate — automated scanning+35
Burst 29/2sAbnormally fast request rate — automated scanning+35
Burst 30/2sAbnormally fast request rate — automated scanning+35
Burst 31/2sAbnormally fast request rate — automated scanning+35
Burst 34/2sAbnormally fast request rate — automated scanning+35
Burst 35/2sAbnormally fast request rate — automated scanning+35
Burst 36/2sAbnormally fast request rate — automated scanning+35
Burst 37/2sAbnormally fast request rate — automated scanning+35
Burst 38/2sAbnormally fast request rate — automated scanning+35
Burst 39/2sAbnormally fast request rate — automated scanning+35
Burst 40/2sAbnormally fast request rate — automated scanning+35
Burst 41/2sAbnormally fast request rate — automated scanning+35
Burst 42/2sAbnormally fast request rate — automated scanning+35
Burst 43/2sAbnormally fast request rate — automated scanning+35
Burst 44/2sAbnormally fast request rate — automated scanning+35
Burst 45/2sAbnormally fast request rate — automated scanning+35
Burst 46/2sAbnormally fast request rate — automated scanning+35
Burst 47/2sAbnormally fast request rate — automated scanning+35
Burst 48/10sAbnormally fast request rate — automated scanning+35
Burst 48/2sAbnormally fast request rate — automated scanning+35
Burst 49/2sAbnormally fast request rate — automated scanning+35
Burst 50/2sAbnormally fast request rate — automated scanning+35
Burst 51/2sAbnormally fast request rate — automated scanning+35
Burst 52/2sAbnormally fast request rate — automated scanning+35
Burst 53/2sAbnormally fast request rate — automated scanning+35
Burst 54/2sAbnormally fast request rate — automated scanning+35
Burst 55/2sAbnormally fast request rate — automated scanning+35
Burst 56/2sAbnormally fast request rate — automated scanning+35
Burst 57/2sAbnormally fast request rate — automated scanning+35
Burst 58/2sAbnormally fast request rate — automated scanning+35
Burst 59/2sAbnormally fast request rate — automated scanning+35
Burst 60/2sAbnormally fast request rate — automated scanning+35
Burst 62/2sAbnormally fast request rate — automated scanning+35
Burst 64/2sAbnormally fast request rate — automated scanning+35
Burst 65/2sAbnormally fast request rate — automated scanning+35
Burst 66/2sAbnormally fast request rate — automated scanning+35
Burst 72/10sAbnormally fast request rate — automated scanning+35
Burst 73/10sAbnormally fast request rate — automated scanning+35
Burst 74/10sAbnormally fast request rate — automated scanning+35
Burst 77/2sAbnormally fast request rate — automated scanning+35
Burst 78/10sAbnormally fast request rate — automated scanning+35
Burst 81/10sAbnormally fast request rate — automated scanning+35
Burst 88/10sAbnormally fast request rate — automated scanning+35
Burst 89/10sAbnormally fast request rate — automated scanning+35
Burst 91/10sAbnormally fast request rate — automated scanning+35
Burst 92/10sAbnormally fast request rate — automated scanning+35
Burst 93/10sAbnormally fast request rate — automated scanning+35
Burst 94/10sAbnormally fast request rate — automated scanning+35
Burst 96/10sAbnormally fast request rate — automated scanning+35
Burst 98/10sAbnormally fast request rate — automated scanning+35
Burst 99/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 100Medium-risk: admin panels, config files+60
Danger medium hits: 104Medium-risk: admin panels, config files+60
Danger medium hits: 111Medium-risk: admin panels, config files+60
Danger medium hits: 114Medium-risk: admin panels, config files+60
Danger medium hits: 118Medium-risk: admin panels, config files+60
Danger medium hits: 132Medium-risk: admin panels, config files+60
Danger medium hits: 135Medium-risk: admin panels, config files+60
Danger medium hits: 141Medium-risk: admin panels, config files+60
Danger medium hits: 144Medium-risk: admin panels, config files+60
Danger medium hits: 147Medium-risk: admin panels, config files+60
Danger medium hits: 159Medium-risk: admin panels, config files+60
Danger medium hits: 168Medium-risk: admin panels, config files+60
Danger medium hits: 171Medium-risk: admin panels, config files+60
Danger medium hits: 174Medium-risk: admin panels, config files+60
Danger medium hits: 182Medium-risk: admin panels, config files+60
Danger medium hits: 185Medium-risk: admin panels, config files+60
Danger medium hits: 188Medium-risk: admin panels, config files+60
Danger medium hits: 228Medium-risk: admin panels, config files+60
Danger medium hits: 240Medium-risk: admin panels, config files+60
Danger medium hits: 270Medium-risk: admin panels, config files+60
Danger medium hits: 278Medium-risk: admin panels, config files+60
Danger medium hits: 328Medium-risk: admin panels, config files+60
Danger medium hits: 376Medium-risk: admin panels, config files+60
Danger medium hits: 404Medium-risk: admin panels, config files+60
Danger medium hits: 48Medium-risk: admin panels, config files+60
Danger medium hits: 74Medium-risk: admin panels, config files+60
Danger medium hits: 88Medium-risk: admin panels, config files+60
Danger medium hits: 90Medium-risk: admin panels, config files+60
Danger medium hits: 94Medium-risk: admin panels, config files+60
Danger medium hits: 96Medium-risk: admin panels, config files+60
Danger medium hits: 98Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 28High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 32High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 37High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 5625
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-08-03 17:40:00
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Burst 100/10s (+35)
2026-08-16 01:04:37
Last malicious request observed
Total score reached: 280/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇳🇴 Norway
06

Recommendations

Actions taken & recommended

  • IP 20.100.172.153 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.100.172.153 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.100.172.153.

🤖 User-Agent Anomaly Defense

IP 20.100.172.153 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
psbl.surriel.com

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

20.100.172.153 has been assigned a threat score of 280/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Network traffic from 20.100.172.153, located in Lorenskog, Norway, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. During its 12-day observation window, we recorded 6,538 hostile requests from this IP — roughly 544.8 per day on average. 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 102 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.

11

Related Threats

🇳🇴 Top threats from Norway

45.13.191.15 (305)20.251.43.72 (280)20.251.15.206 (280)20.251.200.74 (280)20.251.27.23 (280)View all →

🏢 Same network: AS8075

68.155.155.199 (320)20.127.136.245 (318)20.151.200.44 (315)51.13.121.117 (280)20.100.175.1 (280)View all →
12

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.

💡 State-Sponsored Cyber Operations

Nation-state actors conduct sophisticated campaigns for espionage, sabotage, and influence operations. Their resources exceed typical criminal organizations, enabling zero-day exploitation, long-term persistent access, and attacks on critical infrastructure.

🔍 Check Any IP Address

Share this report:
AboutDisclaimerTermsAbuse Reports Tracker
Report generated 10.09.2026 01:51
Behave or get exposed