ABUSE.MOM
THREAT REPORT

IP Threat Report
185.195.24.69

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:54:47
First seen: 2026-05-22 01:17:28
Last seen: 2026-05-24 10:10:30
65

⛔ Verdict: BLOCK

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

BOT_UAUA_CHANGED
01

Geolocation & Classification

IP Address
185.195.24.69
Type
Residential
Country
🇷🇺 Russia
City
Moscow
ISP
First Server Limited
Organization
First Server Limited
Autonomous System
AS204997 FIRST SERVER LIMITED
Hit Count
73
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: curlKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 65
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-05-22 01:17:28
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: curl (+40), UA changed (+25)
2026-05-24 10:10:30
Last malicious request observed
Total score reached: 65/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

First Server Limited
AS204997 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

Address UA spoofing from 185.195.24.69: 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
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

185.195.24.69 has been assigned a threat score of 65/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

185.195.24.69 is registered in Moscow, Russia, operating on the network of First Server Limited. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 2 days in our monitoring system, producing 73 flagged requests at a rate of ~36.5/day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. With 107 flagged addresses, Russia represents a significant presence in our threat database. The score of 65/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

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: AS204997

185.180.230.193 (150)91.217.81.231 (115)185.195.25.207 (70)193.109.78.172 (65)193.109.78.143 (65)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 Passive DNS for Threat Hunting

Passive DNS databases record historical DNS resolution data, enabling analysts to track domain changes, identify related infrastructure, and discover malicious domains sharing hosting with known threats. This historical context is invaluable for threat investigation.

🔍 Check Any IP Address

Share this report: