ABUSE.MOM
THREAT REPORT

IP Threat Report
185.104.248.61

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 13:26:19
First seen: 2026-02-17 17:25:07
Last seen: 2026-05-30 12:11:48
65

⛔ Verdict: BLOCK

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

BOT_UAIMPORTUA_CHANGED
01

Geolocation & Classification

IP Address
185.104.248.61
Type
Hosting
Country
🇷🇺 Russia
City
Moscow
ISP
First Server Limited
Organization
First Server Limited
Autonomous System
AS204997 FIRST SERVER LIMITED
Hit Count
364
02

Detection Signatures

SignatureDescriptionPointsSeverity
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
Σ = 90
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
Imported from old blocklist, UA bot: curl (+40), UA changed (+25)
2026-05-30 12:11:48
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.104.248.61 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.104.248.61: 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
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org

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

10

Threat Analysis

185.104.248.61 has been assigned a threat score of 65/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

Network traffic from 185.104.248.61, located in Moscow, Russia, operating on the network of First Server Limited, has been classified as malicious by our automated threat scoring engine. The address has been active for 101 days in our monitoring system, producing 364 flagged requests at a rate of ~3.6/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. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. Our records show 107 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. At 65/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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

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

💡 TLS Certificate Misconfigurations

Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.

🔍 Check Any IP Address

Share this report: