IP Threat Report
35.231.98.214
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 110/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 116/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 117/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 120/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 123/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 124/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 126/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 128/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 130/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 132/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 134/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 136/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 137/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 139/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 148/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 151/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 157/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 163/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 176/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 14 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 7 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 108 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 31 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 54 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 90 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
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 35.231.98.214 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
🔎 Directory Scan Defense
IP 35.231.98.214 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 35.231.98.214.
🤖 Bot Detection
Address UA spoofing from 35.231.98.214: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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
35.231.98.214 has been assigned a threat score of 303/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
📊 Threat Analysis
Threat intelligence analysis has linked 35.231.98.214 to malicious activity originating from North Charleston, United States, operating on the network of Google LLC. The address has been under observation since its initial detection. Over a period of 3 days, this IP generated 2,543 malicious requests, averaging approximately 847.7 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. United States currently accounts for 128 blocked IPs in our database, making it a significant source of malicious traffic. A score of 303/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
Related Threats
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →Security Intelligence
💡 DDoS Mitigation Approaches
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
💡 Zero-Day Vulnerability Markets
Zero-day vulnerabilities command premium prices in both legitimate and criminal markets. Government agencies, defensive security firms, and criminal organizations compete for these undisclosed flaws, creating a complex ecosystem around vulnerability discovery and disclosure.