ABUSE.MOM
THREAT REPORT

IP Threat Report
4.224.122.112

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-24 18:08:59
First seen: 2026-10-07 09:41:40
Last seen: 2026-10-18 00:11:04
280

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
4.224.122.112
Type
Hosting
Country
🇮🇳 India
City
Pune
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (centralindia)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
6812
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 15/2sAbnormally fast request rate — automated scanning+35
Burst 16/2sAbnormally fast request rate — automated scanning+35
Burst 17/2sAbnormally fast request rate — automated scanning+35
Burst 18/2sAbnormally fast request rate — automated scanning+35
Burst 42/10sAbnormally fast request rate — automated scanning+35
Burst 47/10sAbnormally fast request rate — automated scanning+35
Burst 50/10sAbnormally fast request rate — automated scanning+35
Burst 57/10sAbnormally fast request rate — automated scanning+35
Burst 58/10sAbnormally fast request rate — automated scanning+35
Burst 59/10sAbnormally fast request rate — automated scanning+35
Burst 60/10sAbnormally fast request rate — automated scanning+35
Burst 61/10sAbnormally fast request rate — automated scanning+35
Burst 62/10sAbnormally fast request rate — automated scanning+35
Burst 63/10sAbnormally fast request rate — automated scanning+35
Burst 64/10sAbnormally fast request rate — automated scanning+35
Burst 65/10sAbnormally fast request rate — automated scanning+35
Burst 66/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: 126Medium-risk: admin panels, config files+60
Danger medium hits: 135Medium-risk: admin panels, config files+60
Danger medium hits: 138Medium-risk: admin panels, config files+60
Danger medium hits: 140Medium-risk: admin panels, config files+60
Danger medium hits: 141Medium-risk: admin panels, config files+60
Danger medium hits: 150Medium-risk: admin panels, config files+60
Danger medium hits: 162Medium-risk: admin panels, config files+60
Danger medium hits: 164Medium-risk: admin panels, config files+60
Danger medium hits: 168Medium-risk: admin panels, config files+60
Danger medium hits: 172Medium-risk: admin panels, config files+60
Danger medium hits: 178Medium-risk: admin panels, config files+60
Danger medium hits: 188Medium-risk: admin panels, config files+60
Danger medium hits: 199Medium-risk: admin panels, config files+60
Danger medium hits: 200Medium-risk: admin panels, config files+60
Danger medium hits: 207Medium-risk: admin panels, config files+60
Danger medium hits: 210Medium-risk: admin panels, config files+60
Danger medium hits: 235Medium-risk: admin panels, config files+60
Danger medium hits: 273Medium-risk: admin panels, config files+60
Danger medium hits: 278Medium-risk: admin panels, config files+60
Danger medium hits: 280Medium-risk: admin panels, config files+60
Danger medium hits: 282Medium-risk: admin panels, config files+60
Danger medium hits: 300Medium-risk: admin panels, config files+60
Danger medium hits: 302Medium-risk: admin panels, config files+60
Danger medium hits: 312Medium-risk: admin panels, config files+60
Danger medium hits: 338Medium-risk: admin panels, config files+60
Danger medium hits: 345Medium-risk: admin panels, config files+60
Danger medium hits: 362Medium-risk: admin panels, config files+60
Danger medium hits: 376Medium-risk: admin panels, config files+60
Danger medium hits: 40Medium-risk: admin panels, config files+60
Danger medium hits: 400Medium-risk: admin panels, config files+60
Danger medium hits: 42Medium-risk: admin panels, config files+60
Danger medium hits: 45Medium-risk: admin panels, config files+60
Danger medium hits: 47Medium-risk: admin panels, config files+60
Danger medium hits: 488Medium-risk: admin panels, config files+60
Danger medium hits: 70Medium-risk: admin panels, config files+60
Danger medium hits: 75Medium-risk: admin panels, config files+60
Danger medium hits: 84Medium-risk: admin panels, config files+60
Danger medium hits: 90Medium-risk: admin panels, config files+60
Danger medium hits: 92Medium-risk: admin panels, config files+60
Danger medium hits: 94Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 11High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 17High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 23High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger strong hits: 34High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 7High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 8High-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
Σ = 4490
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-10-07 09:41:40
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 15/2s (+35)
2026-10-18 00:11:04
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 · 🇮🇳 India

We have detected 1852 malicious IPs from this autonomous system.

View all IPs from AS8075 →
06

Recommendations

Actions taken & recommended

  • IP 4.224.122.112 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.224.122.112: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Traffic Flood Defense

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

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

10

Threat Analysis

4.224.122.112 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.224.122.112, geolocated to Pune, India, 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,812 flagged requests at a rate of ~681.2/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 combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 4,286 flagged addresses, India represents a major presence in our threat database. 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 India

49.248.192.204 (313)62.72.43.237 (305)20.197.26.46 (300)34.100.193.82 (295)194.61.40.210 (295)View all →

🏢 Same network: AS8075

68.155.155.199 (320)20.127.136.245 (318)20.151.200.44 (315)20.92.77.159 (310)20.210.128.125 (310)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.

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

🔍 Check Any IP Address

Share this report: