ABUSE.MOM
THREAT REPORT

IP Threat Report
172.68.10.16

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:21:45
First seen: 2026-02-17 17:25:07
Last seen: 2026-05-12 07:01:02
170

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404IMPORTUA_CHANGED
01

Geolocation & Classification

IP Address
172.68.10.16
Type
Hosting
Country
🇷🇺 Russia
City
Moscow
ISP
Cloudflare, Inc.
Organization
Cloudflare WARP
Autonomous System
AS13335 Cloudflare, Inc.
Hit Count
22
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 2Medium-risk: admin panels, config files+20
Σ = 350
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
Danger strong hits: 2 (+50), Danger medium hits: 1 (+10), 404 ratio 40-60% (+15)
2026-05-12 07:01:02
Last malicious request observed
Total score reached: 170/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Cloudflare, Inc.
AS13335 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

  • IP 172.68.10.16 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 172.68.10.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

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

🤖 User-Agent Anomaly Defense

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

07

Neighbors in 172.68.10.0/24

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

09

Blacklist Status (DNSBL)

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

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

172.68.10.16 has been assigned a threat score of 170/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 172.68.10.16 to malicious activity originating from Moscow, Russia, operating on the network of Cloudflare, Inc.. The address has been under observation since its initial detection. During its 83-day observation window, we recorded 22 hostile requests from this IP — roughly 0.3 per day on average. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. With 111 flagged addresses, Russia represents a significant presence in our threat database. With a threat score of 170/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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

172.71.184.70 (200)172.71.184.71 (180)172.71.184.56 (175)172.71.184.98 (175)172.71.184.99 (175)View all →
12

Security Intelligence

💡 Brute Force Attack Mechanics

Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.

💡 Multi-Factor Authentication Importance

MFA dramatically reduces the effectiveness of credential-based attacks. Even when passwords are compromised through phishing or data breaches, the additional authentication factor prevents unauthorized access in the vast majority of cases.

🔍 Check Any IP Address

Share this report: