ABUSE.MOM
THREAT REPORT

IP Threat Report
217.116.58.245

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:28:24
First seen: 2026-04-24 21:00:04
Last seen: 2026-05-10 04:00:07
148

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHMETHODUA_CHANGEDREFERERBURSTUA_SUSRATIO_404
01

Geolocation & Classification

IP Address
217.116.58.245
Type
Residential
Country
🇷🇺 Russia
City
Tyumen
ISP
Russian company LLC
Organization
JSC Russian Company.
Autonomous System
AS15493 Russian company LLC
Hit Count
366
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: node-fetchKnown bot/crawler User-Agent detected+40
Danger medium hits: 66Medium-risk: admin panels, config files+60
POST requests presentBehavioral anomaly detected by automated analysis+8
Danger medium hits: 133Medium-risk: admin panels, config files+60
Danger medium hits: 132Medium-risk: admin panels, config files+60
Danger medium hits: 134Medium-risk: admin panels, config files+60
Danger medium hits: 135Medium-risk: admin panels, config files+60
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Referer points to .php on your siteReferer from unrelated external domain+15
Burst: 13 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 26 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Danger medium hits: 16Medium-risk: admin panels, config files+60
Danger medium hits: 131Medium-risk: admin panels, config files+60
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 137Medium-risk: admin panels, config files+60
Danger medium hits: 130Medium-risk: admin panels, config files+60
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger medium hits: 129Medium-risk: admin panels, config files+60
Danger medium hits: 136Medium-risk: admin panels, config files+60
Danger medium hits: 138Medium-risk: admin panels, config files+60
Danger medium hits: 35Medium-risk: admin panels, config files+60
Danger medium hits: 127Medium-risk: admin panels, config files+60
Danger medium hits: 139Medium-risk: admin panels, config files+60
Danger medium hits: 83Medium-risk: admin panels, config files+60
Danger medium hits: 104Medium-risk: admin panels, config files+60
Σ = 1263
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-24 21:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: node-fetch (+40), Danger medium hits: 66 (+60), POST requests present (+8)
2026-05-10 04:00:07
Last malicious request observed
Total score reached: 148/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Russian company LLC
AS15493 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

  • IP 217.116.58.245 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 217.116.58.0/24
  • 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 217.116.58.245 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 217.116.58.245.

🔎 Path Enumeration Protection

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

07

Neighbors in 217.116.58.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
ix.dnsbl.manitu.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

217.116.58.245 has been assigned a threat score of 148/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

IP address 217.116.58.245 has been traced to Tyumen, Russia, operating on the network of Russian company LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 15 days in our monitoring system, producing 366 flagged requests at a rate of ~24.4/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Our records show 122 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. At 148/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇷🇺 Top threats from Russia

157.22.102.172 (313)178.130.54.159 (288)72.56.191.6 (265)95.182.125.201 (265)91.240.87.225 (263)View all →

🏢 Same network: AS15493

217.116.58.22 (148)217.116.58.230 (148)217.116.58.7 (108)217.116.58.12 (108)217.116.58.47 (108)View all →
12

Security Intelligence

💡 Initial Access Broker Marketplace

Initial access brokers specialize in gaining entry to corporate networks and selling that access to ransomware operators. This specialization creates an efficient criminal marketplace where compromised credentials and VPN access are traded as commodities.

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

🔍 Check Any IP Address

Share this report: