ABUSE.MOM
THREAT REPORT

IP Threat Report
194.67.205.243

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 09:54:23
First seen: 2026-05-03 11:26:32
Last seen: 2026-05-30 09:53:17
100

⛔ Verdict: BLOCK

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

BURSTFORM_SPAMMETHODRATIO_404REDIRECT_PROBEREFERERspam
01

Geolocation & Classification

IP Address
194.67.205.243
Type
Hosting
Country
🇷🇺 Russia
City
Moscow
ISP
I-servers LTD
Organization
I-servers LTD
Autonomous System
AS209641 I-SERVERS LTD
Hit Count
10340
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 5/2sAbnormally fast request rate — automated scanning+35
Burst 6/2sAbnormally fast request rate — automated scanning+35
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Foreign referer seenReferer from unrelated external domain+10
Form spam: no_js_checkSpam/malware keywords in request content+0
POST seenBehavioral anomaly detected by automated analysis+8
Probe 302→404Behavioral anomaly detected by automated analysis+20
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
spam:no_js_checkSpam/malware keywords in request content+0
Σ = 188
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-03 11:26:32
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 5/2s (+35), Burst 6/2s (+35)
2026-05-30 09:53:17
Last malicious request observed
Total score reached: 100/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

I-servers LTD
AS209641 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

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

🌊 Traffic Flood Defense

IP 194.67.205.243 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

📧 Spam Protection

Enable CAPTCHA on all public forms. Add honeypot fields. Rate-limit submissions to 3 per minute per IP. Deploy Akismet or CleanTalk.

08

Open Ports & Services

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

OPEN PORTS (1)
PortServiceRiskDescription
5985UnknownLowService on port 5985
Hostnames: vds2233706.my-ihor.ru
PTR: vds2233706.my-ihor.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
zen.spamhaus.org
✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ 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

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

Threat intelligence analysis has linked 194.67.205.243 to malicious activity originating from Moscow, Russia, operating on the network of I-servers LTD. The address has been under observation since its initial detection. Our sensors captured 10,340 malicious requests from this address across a 26-day span, reflecting a sustained attack cadence of ~397.7 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 116 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. With a threat score of 100/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 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: AS209641

185.5.249.176 (155)185.5.249.66 (155)185.105.116.26 (150)91.217.80.200 (150)185.200.188.234 (130)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.

💡 Responsible Disclosure Ethics

Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.

🔍 Check Any IP Address

Share this report: