ABUSE.MOM
THREAT REPORT

IP Threat Report
85.254.13.161

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 11:49:49
First seen: 2026-03-06 15:00:04
Last seen: 2026-03-06 15:00:04
143

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
85.254.13.161
Type
Residential
Country
🇪🇪 EE
City
Tallinn
ISP
UAB "Bite Lietuva"
Organization
Unknown
Autonomous System
AS199527 UAB "Bite Lietuva"
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: pythonKnown bot/crawler User-Agent detected+40
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
Σ = 143
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-06 15:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: python (+40), Danger strong hits: 3 (+75), Danger medium hits: 2 (+20)
2026-03-06 15:00:04
Last malicious request observed
Total score reached: 143/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

UAB "Bite Lietuva"
AS199527 · 🇪🇪 EE
06

Recommendations

Actions taken & recommended

  • IP 85.254.13.161 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 85.254.13.161: 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
Spamhaus ZEN

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

10

Threat Analysis

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

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

Network traffic from 85.254.13.161, located in Tallinn, EE, operating on the network of UAB "Bite Lietuva", has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. With 39 flagged addresses, EE represents a notable presence in our threat database. A score of 143/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 EE

5.157.5.149 (150)165.231.164.197 (140)140.99.201.129 (140)196.196.222.46 (140)5.157.5.62 (140)View all →

🏢 Same network: AS199527

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.

💡 Race Condition Vulnerabilities

Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.

🔍 Check Any IP Address

Share this report: