IP Threat Report
69.160.102.226
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Foreign referer | Referer from unrelated external domain | +10 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 69.160.102.226 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 69.160.102.0/24
- 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 69.160.102.226: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Neighbors in 69.160.102.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
69.160.102.226 has been assigned a threat score of 60/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
The following attack categories were identified:
📊 Threat Analysis
The address 69.160.102.226 originates from Kingston, JM, operating on the network of Digicel Jamaica. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 100 malicious requests from this address across a 4-day span, reflecting a sustained attack cadence of ~25 requests per day. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 34 malicious IPs originating from JM, positioning it as a notable contributor to global threat activity. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
Related Threats
🇯🇲 Top threats from JM
83.219.96.25 (255)83.219.96.26 (255)83.219.96.28 (255)83.219.96.27 (255)83.219.96.24 (255)View all →🏢 Same network: AS40786
69.160.102.237 (103)63.143.95.26 (103)63.143.116.80 (95)69.160.113.116 (83)69.160.102.93 (75)View all →Security Intelligence
💡 Directory Traversal Attacks
Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.
💡 WordPress-Specific Attack Vectors
WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.