ABUSE.MOM
THREAT REPORT

IP Threat Report
185.128.107.128

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 12:06:55
First seen: 2026-02-17 17:25:07
Last seen: 2026-05-30 12:01:01
155

⛔ Verdict: BLOCK

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

BOT_UABURSTIMPORTREDIRECT_PROBEUA_CHANGED
01

Geolocation & Classification

IP Address
185.128.107.128
Type
Hosting
Country
🇷🇺 Russia
City
Moscow
ISP
First Server Limited
Organization
Firstbyte Hosting
Autonomous System
AS205090 FIRST SERVER LIMITED
Hit Count
435
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 13 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 9 req / 2sAbnormally fast request rate — automated scanning+35
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
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
Σ = 180
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-02-17 17:25:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 13 req / 10s (+35), Burst: 9 req / 2s (+35), Imported from old blocklist
2026-05-30 12:01:01
Last malicious request observed
Total score reached: 155/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

First Server Limited
AS205090 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

🌊 Traffic Flood Defense

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

🔎 Path Enumeration Protection

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

🤖 User-Agent Anomaly Defense

IP 185.128.107.128 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

09

Blacklist Status (DNSBL)

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

✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
bl.blocklist.de
✓ Clean
bl.spamcop.net

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

10

Threat Analysis

185.128.107.128 has been assigned a threat score of 155/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request FloodingPath EnumerationUser-Agent Anomaly

📊 Threat Analysis

185.128.107.128 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. Our sensors captured 435 malicious requests from this address across a 101-day span, reflecting a sustained attack cadence of ~4.3 requests per 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 diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Russia currently accounts for 110 blocked IPs in our database, making it a significant source of malicious traffic. A score of 155/100 places this address in the top tier of severity. Block and investigate any historical connections.

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

89.44.87.68 (150)193.162.143.246 (125)89.44.86.199 (90)45.9.75.13 (65)89.44.87.54 (65)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.

💡 Network Flow Analysis

Analyzing network flows (NetFlow, sFlow, IPFIX) provides visibility into traffic patterns without inspecting packet contents. Flow data reveals scanning activity, data exfiltration, lateral movement, and command-and-control channels at scale.

🔍 Check Any IP Address

Share this report: