ABUSE.MOM
THREAT REPORT

IP Threat Report
135.116.194.58

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 21:05:51
First seen: 2026-04-10 17:00:05
Last seen: 2026-04-11 05:00:08
245

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATHBURSTRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
135.116.194.58
Type
Hosting
Country
🇸🇪 Sweden
City
Gävle
ISP
MICROSOFT
Organization
Microsoft Azure Cloud (swedencentral)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
21
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 516Medium-risk: admin panels, config files+60
Burst: 60 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 193 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 387Medium-risk: admin panels, config files+60
Burst: 66 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 200 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 258Medium-risk: admin panels, config files+60
Burst: 34 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 116 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 55 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 196 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 64 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 59 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 185 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 53 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 165 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 63 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 49 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 156 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 44 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 140 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 158 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 257Medium-risk: admin panels, config files+60
Burst: 41 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 132 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 256Medium-risk: admin panels, config files+60
Burst: 35 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 114 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 43 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 127 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 123 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 68 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 40 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 115 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 65 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 61 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 71 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 1795
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-04-10 17:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA suspicious (short/empty) (+15), Danger strong hits: 6 (+100), Danger medium hits: 516 (+60)
2026-04-11 05:00:08
Last malicious request observed
Total score reached: 245/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

MICROSOFT
AS8075 · 🇸🇪 Sweden
06

Recommendations

Actions taken & recommended

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

🤖 User-Agent Anomaly Defense

IP 135.116.194.58 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🌊 Flood / DDoS Mitigation

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

🔎 Path Enumeration Protection

Block scanning from 135.116.194.58: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

09

Blacklist Status (DNSBL)

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

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

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

User-Agent AnomalyRequest FloodingPath Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 135.116.194.58 to malicious activity originating from Gävle, Sweden, operating on the network of MICROSOFT. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 21 flagged requests at a rate of ~21/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Sweden currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 245/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 Sweden

74.241.249.229 (340)91.92.42.63 (300)91.92.42.120 (300)51.107.182.56 (280)20.91.197.150 (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

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 DNS Amplification Attack Mechanics

DNS amplification exploits open resolvers to reflect and amplify traffic toward victims. A small query triggers a large response directed at the spoofed source IP, achieving amplification factors of 50x or more, overwhelming target bandwidth.

🔍 Check Any IP Address

Share this report: