ABUSE.MOM
THREAT REPORT

IP Threat Report
62.3.58.245

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 01:44:50
First seen: 2026-03-22 16:00:06
Last seen: 2026-03-24 04:00:06
140

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEBURSTREFERER
01

Geolocation & Classification

IP Address
62.3.58.245
Type
Residential
Country
🇷🇺 Russia
City
Moscow
ISP
FOP Hornostay Mykhaylo Ivanovych
Organization
FOP Hornostay Mykhaylo Ivanovych
Autonomous System
AS212913 FOP Hornostay Mykhaylo Ivanovych
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 10Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Danger medium hits: 2Medium-risk: admin panels, config files+20
Σ = 160
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-03-22 16:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 10 (+60), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-03-24 04:00:06
Last malicious request observed
Total score reached: 140/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

FOP Hornostay Mykhaylo Ivanovych
AS212913 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

  • IP 62.3.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 62.3.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

🔎 Path Enumeration Protection

Block scanning from 62.3.58.245: 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 62.3.58.245.

07

Neighbors in 62.3.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
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.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

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

Path EnumerationRequest Flooding

📊 Threat Analysis

The address 62.3.58.245 originates from Moscow, Russia, operating on the network of FOP Hornostay Mykhaylo Ivanovych. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 1 days in our monitoring system, producing 2 flagged requests at a rate of ~2/day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. At 140/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

62.3.58.9 (140)81.22.193.177 (140)89.221.204.53 (140)81.22.193.14 (140)89.221.204.136 (140)View all →

🏢 Same network: AS212913

62.3.58.9 (140)81.22.193.177 (140)89.221.204.53 (140)81.22.193.14 (140)89.221.204.136 (140)View all →
12

Security Intelligence

💡 Directory Traversal Attacks

Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.

💡 Behavioral Analysis vs Signature Detection

Signature-based detection matches known attack patterns but misses novel threats. Behavioral analysis identifies anomalies in request patterns, timing, and volume, catching zero-day attacks that signatures cannot recognize.

🔍 Check Any IP Address

Share this report: