ABUSE.MOM
THREAT REPORT

IP Threat Report
135.119.49.97

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 21:03:29
First seen: 2026-05-22 16:45:21
Last seen: 2026-05-24 10:21:00
280

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
135.119.49.97
Type
Hosting
Country
🇺🇸 United States
City
Des Moines
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (centralus)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
420
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 17/2sAbnormally fast request rate — automated scanning+35
Burst 18/2sAbnormally fast request rate — automated scanning+35
Burst 19/2sAbnormally fast request rate — automated scanning+35
Burst 54/10sAbnormally fast request rate — automated scanning+35
Burst 60/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 65/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 202Medium-risk: admin panels, config files+60
Danger medium hits: 204Medium-risk: admin panels, config files+60
Danger medium hits: 303Medium-risk: admin panels, config files+60
Danger medium hits: 306Medium-risk: admin panels, config files+60
Danger strong hits: 4High-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
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 870
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-22 16:45:21
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 17/2s (+35), Burst 18/2s (+35)
2026-05-24 10:21:00
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 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 135.119.49.97 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 135.119.49.0/24
  • 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 135.119.49.97: 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 135.119.49.97.

🤖 Bot Detection

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

07

Neighbors in 135.119.49.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

135.119.49.97 has been assigned a threat score of 280/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:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 135.119.49.97 has been traced to Des Moines, United States, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 420 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~420 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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 102 flagged addresses, United States represents a significant 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 United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)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.

💡 Threat Intelligence Sharing Frameworks

Standards like STIX/TAXII, MISP, and OpenIOC enable automated sharing of threat intelligence between organizations. Collective defense through shared indicators, tactics, and procedures strengthens the entire security community against common threats.

🔍 Check Any IP Address

Share this report: