IP Threat Report
136.110.71.187
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 | |
| Burst 64/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 96/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Danger strong hits: 135 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
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 136.110.71.187 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 136.110.71.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 136.110.71.187: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 136.110.71.187.
🤖 Bot Detection
Address UA spoofing from 136.110.71.187: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Neighbors in 136.110.71.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
136.110.71.187 has been assigned a threat score of 270/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:
📊 Threat Analysis
Network traffic from 136.110.71.187, located in Tokyo, Japan, operating on the network of Google LLC, has been classified as malicious by our automated threat scoring engine. The address has been active for 1 days in our monitoring system, producing 55 flagged requests at a rate of ~55/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 102 flagged addresses, Japan represents a significant presence in our threat database. With a threat score of 270/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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
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.
💡 Threat Score Calculation Methods
Threat scoring combines multiple signals — request patterns, known signatures, IP reputation, geographic risk, and behavioral analysis — into a single actionable metric. Weighted scoring models allow tuning sensitivity to balance security with usability.