IP Threat Report
176.28.170.254
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| POST requests present | Behavioral anomaly detected by automated analysis | +8 |
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 176.28.170.254 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
🤖 User-Agent Anomaly Defense
IP 176.28.170.254 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🔎 Directory Scan Defense
IP 176.28.170.254 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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
176.28.170.254 has been assigned a threat score of 128/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
📊 Threat Analysis
Our monitoring infrastructure has identified 176.28.170.254, geolocated to Amman, JO, operating on the network of ZAIN, as a source of suspicious network activity. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 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. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. JO currently accounts for 78 blocked IPs in our database, making it a notable source of malicious traffic. A score of 128/100 places this address in the top tier of severity. Block and investigate any historical connections.
Related Threats
🇯🇴 Top threats from JO
91.186.252.91 (208)176.29.225.112 (198)91.186.255.110 (168)109.107.243.93 (128)46.185.192.236 (103)View all →🏢 Same network: AS48832
176.29.225.112 (198)176.29.249.183 (103)176.28.155.119 (83)176.28.168.249 (83)176.28.133.231 (75)View all →Security Intelligence
💡 TLS Fingerprinting (JA3/JA4)
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
💡 DNS Sinkholing for Malware Defense
DNS sinkholing redirects queries for known malicious domains to controlled IP addresses. This technique blocks malware communication, prevents data exfiltration, and identifies compromised internal hosts attempting to contact command-and-control servers.