ABUSE.MOM
THREAT REPORT

IP Threat Report
200.68.172.175

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:43:39
First seen: 2026-05-21 23:31:53
Last seen: 2026-05-24 10:19:55
85

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
200.68.172.175
Type
Mobile
Country
🇲🇽 Mexico
City
Tapachula
ISP
RadioMovil Dipsa, S.A. de C.V.
Organization
RadioMovil Dipsa, S.A. de C.V
Autonomous System
AS28403 RadioMovil Dipsa, S.A. de C.V.
Hit Count
268
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Foreign refererReferer from unrelated external domain+10
Σ = 85
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-21 23:31:53
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger strong hits: 2 (+50), Foreign referer (+10)
2026-05-24 10:19:55
Last malicious request observed
Total score reached: 85/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

RadioMovil Dipsa, S.A. de C.V.
AS28403 · 🇲🇽 Mexico
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

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

09

Blacklist Status (DNSBL)

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

✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
zen.spamhaus.org

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

10

Threat Analysis

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

Path Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 200.68.172.175, geolocated to Tapachula, Mexico, operating on the network of RadioMovil Dipsa, S.A. de C.V., as a source of suspicious network activity. Our sensors captured 268 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~134 requests per day. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 122 flagged addresses, Mexico represents a significant presence in our threat database. At 85/100, this IP warrants immediate defensive action.

11

Related Threats

🇲🇽 Top threats from Mexico

158.23.144.198 (280)68.155.145.150 (280)68.155.146.66 (280)34.51.104.11 (263)104.243.245.4 (255)View all →

🏢 Same network: AS28403

View all →
12

Security Intelligence

💡 Vulnerability Scanning Explained

Vulnerability scanning is the automated process of probing web applications for known weaknesses. Attackers use tools like Nuclei, Nikto, and ZAP to test thousands of hosts per hour, looking for exposed configuration files, outdated software, and default credentials.

💡 Security Header Best Practices

HTTP security headers provide defense-in-depth with minimal implementation effort. Key headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy, each addressing specific attack vectors.

🔍 Check Any IP Address

Share this report: