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

IP Threat Report
20.251.112.224

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 12:45:03
First seen: 2026-08-06 12:43:26
Last seen: 2026-08-16 01:03:17
280

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 101/10sAbnormally fast request rate — automated scanning+35
Burst 104/10sAbnormally fast request rate — automated scanning+35
Burst 106/10sAbnormally fast request rate — automated scanning+35
Burst 108/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 113/10sAbnormally fast request rate — automated scanning+35
Burst 115/10sAbnormally fast request rate — automated scanning+35
Burst 116/10sAbnormally fast request rate — automated scanning+35
Burst 117/10sAbnormally fast request rate — automated scanning+35
Burst 118/10sAbnormally fast request rate — automated scanning+35
Burst 119/10sAbnormally fast request rate — automated scanning+35
Burst 124/10sAbnormally fast request rate — automated scanning+35
Burst 126/10sAbnormally fast request rate — automated scanning+35
Burst 131/10sAbnormally fast request rate — automated scanning+35
Burst 132/10sAbnormally fast request rate — automated scanning+35
Burst 135/10sAbnormally fast request rate — automated scanning+35
Burst 137/10sAbnormally fast request rate — automated scanning+35
Burst 141/10sAbnormally fast request rate — automated scanning+35
Burst 143/10sAbnormally fast request rate — automated scanning+35
Burst 144/10sAbnormally fast request rate — automated scanning+35
Burst 145/10sAbnormally fast request rate — automated scanning+35
Burst 151/10sAbnormally fast request rate — automated scanning+35
Burst 152/10sAbnormally fast request rate — automated scanning+35
Burst 153/10sAbnormally fast request rate — automated scanning+35
Burst 158/10sAbnormally fast request rate — automated scanning+35
Burst 175/10sAbnormally fast request rate — automated scanning+35
Burst 186/10sAbnormally fast request rate — automated scanning+35
Burst 191/10sAbnormally fast request rate — automated scanning+35
Burst 200/10sAbnormally 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 32/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 39/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/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 54/2sAbnormally fast request rate — automated scanning+35
Burst 56/2sAbnormally fast request rate — automated scanning+35
Burst 58/2sAbnormally fast request rate — automated scanning+35
Burst 63/2sAbnormally fast request rate — automated scanning+35
Burst 73/10sAbnormally fast request rate — automated scanning+35
Burst 89/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
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 129Medium-risk: admin panels, config files+60
Danger medium hits: 137Medium-risk: admin panels, config files+60
Danger medium hits: 140Medium-risk: admin panels, config files+60
Danger medium hits: 147Medium-risk: admin panels, config files+60
Danger medium hits: 149Medium-risk: admin panels, config files+60
Danger medium hits: 150Medium-risk: admin panels, config files+60
Danger medium hits: 205Medium-risk: admin panels, config files+60
Danger medium hits: 213Medium-risk: admin panels, config files+60
Danger medium hits: 217Medium-risk: admin panels, config files+60
Danger medium hits: 221Medium-risk: admin panels, config files+60
Danger medium hits: 260Medium-risk: admin panels, config files+60
Danger medium hits: 274Medium-risk: admin panels, config files+60
Danger medium hits: 276Medium-risk: admin panels, config files+60
Danger medium hits: 320Medium-risk: admin panels, config files+60
Danger medium hits: 416Medium-risk: admin panels, config files+60
Danger medium hits: 646Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 20High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 22High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 33High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 40High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 42High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 80High-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
Σ = 3970
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-06 12:43:26
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 101/10s (+35), Burst 104/10s (+35)
2026-08-16 01:03:17
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.251.112.224 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

🔎 Path Enumeration Protection

Block scanning from 20.251.112.224: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.251.112.224.

🤖 Bot Detection

Address UA spoofing from 20.251.112.224: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

20.251.112.224 has been assigned a threat score of 280/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 20.251.112.224, geolocated to Lorenskog, Norway, operating on the network of Microsoft Corporation, as a source of suspicious network activity. Our sensors captured 2,987 malicious requests from this address across a 9-day span, reflecting a sustained attack cadence of ~331.9 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With a threat score of 280/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.

11

Related Threats

🇳🇴 Top threats from Norway

51.120.79.193 (280)20.251.48.208 (280)20.100.169.152 (280)51.120.76.82 (280)20.100.198.199 (280)View all →

🏢 Same network: AS8075

68.155.155.199 (320)20.127.136.245 (318)20.151.200.44 (315)20.220.203.117 (280)20.79.30.30 (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.

💡 Content Delivery Network Risks

CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.

🔍 Check Any IP Address

Share this report:
AboutDisclaimerTermsAbuse Reports Tracker
Report generated 13.09.2026 12:45
Behave or get exposed