THREAT REPORT
IP Threat Report
4.225.166.222
ABUSE.MOM — BEHAVE OR GET EXPOSED
01
Geolocation & Classification
IP Address
4.225.166.222
Type
Hosting
Country
🇸🇪 Sweden
City
Gävle
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (swedencentral)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
6158
02
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 100/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 103/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 108/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 11/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 112/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 113/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 115/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 116/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 119/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 121/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 122/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 124/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 126/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 127/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 129/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 130/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 134/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 138/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 139/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 147/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 149/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 150/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 152/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 157/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 158/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 169/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 191/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 193/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 195/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 199/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 29/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 30/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 31/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 32/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 33/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 35/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 37/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 37/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 39/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 40/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 42/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 43/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 44/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 48/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 49/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 51/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 53/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 53/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 55/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 56/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 59/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 62/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 63/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 67/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 68/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 72/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 78/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 80/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 83/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 84/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 88/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 89/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 93/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 94/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 97/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 98/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 99/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 100 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 103 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 104 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 106 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 116 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 122 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 123 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 139 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 151 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 168 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 187 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 188 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 189 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 193 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 194 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 195 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 198 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 218 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 256 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 274 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 277 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 278 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 281 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 349 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 351 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 37 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 411 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 417 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 418 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 500 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 524 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 53 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 66 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 84 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 94 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 10 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 16 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 25 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 34 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 35 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 37 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 40 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 46 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 56 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 64 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 7 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
Σ = 6905
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-07-29 14:39:43
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-09 04:16:57
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.225.166.222 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 4.225.166.222: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 4.225.166.222 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
🤖 Bot Detection
Address UA spoofing from 4.225.166.222: 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
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
bl.spamcop.net
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
10
Threat Analysis
4.225.166.222 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
Our monitoring infrastructure has identified 4.225.166.222, geolocated to Gävle, Sweden, operating on the network of Microsoft Corporation, as a source of suspicious network activity. The address has been active for 10 days in our monitoring system, producing 6,158 flagged requests at a rate of ~615.8/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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. A score of 280/100 places this address in the top tier of severity. Block and investigate any historical connections.
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
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.
💡 Prototype Pollution Attacks
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.
🔍 Check Any IP Address
Share this report: