ABUSE.MOM
THREAT REPORT

IP Threat Report
172.68.10.133

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 10:17:13
First seen: 2026-05-06 05:00:05
Last seen: 2026-05-30 10:00:15
150

⛔ Verdict: BLOCK

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

DANGER_PATH
01

Geolocation & Classification

IP Address
172.68.10.133
Type
VPN
Country
🇷🇺 Russia
City
Moscow
ISP
Cloudflare, Inc.
Organization
Cloudflare WARP
Autonomous System
AS13335 Cloudflare, Inc.
Hit Count
485
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger medium hits: 4Medium-risk: admin panels, config files+40
Danger medium hits: 5Medium-risk: admin panels, config files+50
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
Σ = 430
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-05-06 05:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 1 (+10), Danger medium hits: 3 (+30), Danger medium hits: 4 (+40)
2026-05-30 10:00:15
Last malicious request observed
Total score reached: 150/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.133 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

⚙️ General Security

Add 172.68.10.133 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

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.

✓ Clean
bl.spamcop.net
✓ Clean
cbl.abuseat.org
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
bl.blocklist.de

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

10

Threat Analysis

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

📊 Threat Analysis

172.68.10.133 is registered in Moscow, Russia, operating on the network of Cloudflare, Inc.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 24 days in our monitoring system, producing 485 flagged requests at a rate of ~20.2/day. Classified as a VPN or proxy server, this IP serves as an anonymization layer. While VPNs have legitimate uses, this address has been observed routing clearly malicious traffic. Russia currently accounts for 112 blocked IPs in our database, making it a significant source of malicious traffic. A score of 150/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

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

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 Subdomain Takeover Vulnerabilities

Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.

🔍 Check Any IP Address

Share this report: