ABUSE.MOM
THREAT REPORT

IP Threat Report
194.67.204.55

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:32:42
First seen: 2026-02-17 17:25:07
Last seen: 2026-05-24 10:10:36
90

⛔ Verdict: BLOCK

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

BOT_UAIMPORTRATIO_404UA_CHANGED
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
UA bot: curlKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Σ = 115
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-02-17 17:25:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Imported from old blocklist, UA bot: curl (+40)
2026-05-24 10:10:36
Last malicious request observed
Total score reached: 90/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.204.55 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.204.55: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 Bot Detection

Address UA spoofing from 194.67.204.55: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

09

Blacklist Status (DNSBL)

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

✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
cbl.abuseat.org
✓ Clean
b.barracudacentral.org
✓ Clean
bl.blocklist.de
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net

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

10

Threat Analysis

194.67.204.55 has been assigned a threat score of 90/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

IP address 194.67.204.55 has been traced to Moscow, Russia, operating on the network of I-servers LTD. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 95 days in our monitoring system, producing 127 flagged requests at a rate of ~1.3/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. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Russia currently accounts for 116 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 90/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

💡 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.

💡 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.

🔍 Check Any IP Address

Share this report: