ABUSE.MOM
THREAT REPORT

IP Threat Report
20.198.3.37

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 10:02:26
First seen: 2026-05-17 10:00:05
Last seen: 2026-05-24 10:01:13
230

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

IP Address
20.198.3.37
Type
Hosting
Country
🇮🇳 India
City
Pune
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (centralindia)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
459
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 19/2sAbnormally fast request rate — automated scanning+35
Burst 48/10sAbnormally fast request rate — automated scanning+35
Burst: 19 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 48 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 40Medium-risk: admin panels, config files+60
Danger strong hits: 11High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 13High-risk paths: shells, RCE vectors, exploits+100
Σ = 400
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-05-17 10:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 19/2s (+35), Burst 48/10s (+35), Burst: 19 req / 2s (+35)
2026-05-24 10:01:13
Last malicious request observed
Total score reached: 230/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇮🇳 India
06

Recommendations

Actions taken & recommended

  • IP 20.198.3.37 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

🌊 Flood / DDoS Mitigation

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

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

20.198.3.37 has been assigned a threat score of 230/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 20.198.3.37, geolocated to Pune, India, operating on the network of Microsoft Corporation, as a source of suspicious network activity. Over a period of 7 days, this IP generated 459 malicious requests, averaging approximately 65.6 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. With 101 flagged addresses, India represents a significant presence in our threat database. A score of 230/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

🇮🇳 Top threats from India

49.248.192.204 (313)62.72.43.237 (305)4.188.251.0 (280)103.78.247.150 (280)40.80.90.214 (280)View all →

🏢 Same network: AS8075

74.241.249.229 (340)20.151.111.128 (308)4.182.24.88 (285)20.65.61.3 (283)4.205.39.97 (283)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.

💡 Web Application Firewall Strategies

WAFs inspect HTTP traffic to block common attacks but require careful tuning. Overly aggressive rules cause false positives while permissive configurations miss attacks. Modern WAFs combine signature matching with behavioral analysis and machine learning.

🔍 Check Any IP Address

Share this report: