ABUSE.MOM
THREAT REPORT

IP Threat Report
5.206.16.172

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 12:39:45
First seen: 2026-03-21 11:00:05
Last seen: 2026-03-21 11:00:05
103

⛔ Verdict: BLOCK

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

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
5.206.16.172
Type
Residential
Country
🇷🇺 Russia
City
Troitsk
ISP
Intersvyaz-2 JSC
Organization
Unknown
Autonomous System
AS8369 Intersvyaz-2 JSC
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 103
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-03-21 11:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Danger medium hits: 2 (+20), POST requests present (+8)
2026-03-21 11:00:05
Last malicious request observed
Total score reached: 103/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Intersvyaz-2 JSC
AS8369 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

⚙️ Defensive Recommendations

Block 5.206.16.172 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (1)
PortServiceRiskDescription
7547UnknownLowService on port 7547
Hostnames: pool-5-206-16-172.is74.ru
PTR: pool-5-206-16-172.is74.ru

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

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
dnsbl-1.uceprotect.net
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
bl.spamcop.net

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

10

Threat Analysis

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

📊 Threat Analysis

The address 5.206.16.172 originates from Troitsk, Russia, operating on the network of Intersvyaz-2 JSC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Our records show 111 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. With a threat score of 103/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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)95.182.125.201 (265)72.56.191.6 (265)91.240.87.225 (263)View all →

🏢 Same network: AS8369

78.29.52.101 (103)78.29.34.53 (80)77.222.108.217 (70)176.226.235.228 (70)77.222.107.188 (70)View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 Log Correlation and SIEM Integration

Correlating logs across web servers, firewalls, DNS, and authentication systems reveals attack patterns invisible in individual log sources. Modern SIEM platforms use statistical analysis to connect related events across time and systems.

🔍 Check Any IP Address

Share this report: