ABUSE.MOM
THREAT REPORT

IP Threat Report
4.223.171.122

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 02:25:26
First seen: 2026-08-06 14:46:16
Last seen: 2026-08-23 02:06:53
280

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
4.223.171.122
Type
Hosting
Country
🇸🇪 Sweden
City
Gävle
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (swedencentral)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
4730
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 102/10sAbnormally fast request rate — automated scanning+35
Burst 103/10sAbnormally fast request rate — automated scanning+35
Burst 104/10sAbnormally fast request rate — automated scanning+35
Burst 107/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 112/10sAbnormally fast request rate — automated scanning+35
Burst 113/10sAbnormally fast request rate — automated scanning+35
Burst 114/10sAbnormally fast request rate — automated scanning+35
Burst 118/10sAbnormally fast request rate — automated scanning+35
Burst 120/10sAbnormally fast request rate — automated scanning+35
Burst 121/10sAbnormally fast request rate — automated scanning+35
Burst 122/10sAbnormally fast request rate — automated scanning+35
Burst 124/10sAbnormally fast request rate — automated scanning+35
Burst 127/10sAbnormally fast request rate — automated scanning+35
Burst 130/10sAbnormally fast request rate — automated scanning+35
Burst 132/10sAbnormally fast request rate — automated scanning+35
Burst 133/10sAbnormally fast request rate — automated scanning+35
Burst 134/10sAbnormally fast request rate — automated scanning+35
Burst 138/10sAbnormally fast request rate — automated scanning+35
Burst 140/10sAbnormally fast request rate — automated scanning+35
Burst 142/10sAbnormally fast request rate — automated scanning+35
Burst 144/10sAbnormally fast request rate — automated scanning+35
Burst 149/10sAbnormally fast request rate — automated scanning+35
Burst 150/10sAbnormally fast request rate — automated scanning+35
Burst 152/10sAbnormally fast request rate — automated scanning+35
Burst 156/10sAbnormally fast request rate — automated scanning+35
Burst 162/10sAbnormally fast request rate — automated scanning+35
Burst 163/10sAbnormally fast request rate — automated scanning+35
Burst 164/10sAbnormally fast request rate — automated scanning+35
Burst 165/10sAbnormally fast request rate — automated scanning+35
Burst 168/10sAbnormally fast request rate — automated scanning+35
Burst 172/10sAbnormally fast request rate — automated scanning+35
Burst 175/10sAbnormally fast request rate — automated scanning+35
Burst 178/10sAbnormally fast request rate — automated scanning+35
Burst 181/10sAbnormally fast request rate — automated scanning+35
Burst 182/10sAbnormally fast request rate — automated scanning+35
Burst 196/10sAbnormally fast request rate — automated scanning+35
Burst 197/10sAbnormally fast request rate — automated scanning+35
Burst 200/10sAbnormally fast request rate — automated scanning+35
Burst 28/2sAbnormally fast request rate — automated scanning+35
Burst 29/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 33/2sAbnormally fast request rate — automated scanning+35
Burst 35/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/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 77/10sAbnormally fast request rate — automated scanning+35
Burst 93/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: 107Medium-risk: admin panels, config files+60
Danger medium hits: 140Medium-risk: admin panels, config files+60
Danger medium hits: 146Medium-risk: admin panels, config files+60
Danger medium hits: 150Medium-risk: admin panels, config files+60
Danger medium hits: 196Medium-risk: admin panels, config files+60
Danger medium hits: 212Medium-risk: admin panels, config files+60
Danger medium hits: 213Medium-risk: admin panels, config files+60
Danger medium hits: 215Medium-risk: admin panels, config files+60
Danger medium hits: 26Medium-risk: admin panels, config files+60
Danger medium hits: 260Medium-risk: admin panels, config files+60
Danger medium hits: 262Medium-risk: admin panels, config files+60
Danger medium hits: 263Medium-risk: admin panels, config files+60
Danger medium hits: 317Medium-risk: admin panels, config files+60
Danger medium hits: 337Medium-risk: admin panels, config files+60
Danger medium hits: 395Medium-risk: admin panels, config files+60
Danger medium hits: 428Medium-risk: admin panels, config files+60
Danger medium hits: 430Medium-risk: admin panels, config files+60
Danger medium hits: 526Medium-risk: admin panels, config files+60
Danger medium hits: 618Medium-risk: admin panels, config files+60
Danger medium hits: 674Medium-risk: admin panels, config files+60
Danger medium hits: 994Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 128High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 179High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 180High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 20High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 23High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 269High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 40High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 44High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 88High-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
Σ = 5355
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 14:46:16
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-23 02:06:53
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 · 🇸🇪 Sweden
06

Recommendations

Actions taken & recommended

  • IP 4.223.171.122 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 4.223.171.122 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

IP 4.223.171.122 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 User-Agent Anomaly Defense

IP 4.223.171.122 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
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

4.223.171.122 has been assigned a threat score of 280/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 4.223.171.122 to malicious activity originating from Gävle, Sweden, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Over a period of 16 days, this IP generated 4,730 malicious requests, averaging approximately 295.6 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. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Our records show 101 malicious IPs originating from Sweden, 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.

11

Related Threats

🇸🇪 Top threats from Sweden

74.241.249.229 (340)91.92.42.86 (300)91.92.42.182 (300)91.92.42.63 (300)91.92.42.120 (300)View all →

🏢 Same network: AS8075

4.223.175.204 (280)4.223.83.61 (280)20.240.51.74 (280)20.91.188.128 (280)20.91.198.61 (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.

💡 Botnet Command and Control Evolution

Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.

🔍 Check Any IP Address

Share this report: