ABUSE.MOM
THREAT REPORT

IP Threat Report
185.177.72.12

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:22:00
First seen: 2026-04-11 14:00:04
Last seen: 2026-04-11 14:00:04
328

⛔ Verdict: BLOCK

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

BOT_UAUA_CHANGEDDANGER_PATHRATIO_404BURSTMETHOD
01

Geolocation & Classification

IP Address
185.177.72.12
Type
Residential
Country
🇫🇷 France
City
Vélizy-Villacoublay
ISP
Bucklog SARL
Organization
FBW NETWORKS
Autonomous System
AS211590 Bucklog SARL
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: curlKnown bot/crawler User-Agent detected+40
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 983High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 289Medium-risk: admin panels, config files+60
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 56 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 200 req / 10sAbnormally fast request rate — automated scanning+35
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 328
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-04-11 14:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: curl (+40), UA changed for same IP (+25), Danger strong hits: 983 (+100)
2026-04-11 14:00:04
Last malicious request observed
Total score reached: 328/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Bucklog SARL
AS211590 · 🇫🇷 France
06

Recommendations

Actions taken & recommended

  • IP 185.177.72.12 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 185.177.72.0/24
  • 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.177.72.12: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🔎 Directory Scan Defense

IP 185.177.72.12 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

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

07

Neighbors in 185.177.72.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (2)
PortServiceRiskDescription
22SSHLowSecure Shell — common brute force target for remote access
123UnknownLowService on port 123
DETECTED TECHNOLOGIES
openbsd:openssh:9.2p1ntp:ntp:3debian:debian_linuxlinux:linux_kernel

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

⛔ LISTED
dnsbl-1.uceprotect.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

185.177.72.12 has been assigned a threat score of 328/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:

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

185.177.72.12 is registered in Vélizy-Villacoublay, France, operating on the network of Bucklog SARL. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Our records show 201 malicious IPs originating from France, positioning it as a significant contributor to global threat activity. With a threat score of 328/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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 France

185.177.72.11 (348)185.177.72.10 (348)185.177.72.69 (348)185.177.72.29 (348)185.177.72.23 (348)View all →

🏢 Same network: AS211590

185.177.72.11 (348)185.177.72.10 (348)185.177.72.69 (348)185.177.72.29 (348)185.177.72.23 (348)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

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