ABUSE.MOM
THREAT REPORT

IP Threat Report
136.108.4.250

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-08 15:52:31
First seen: 2026-08-06 05:13:17
Last seen: 2026-08-09 04:10:57
85

⛔ Verdict: BLOCK

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

BURSTRATIO_404UA_CHANGED
01

Geolocation & Classification

IP Address
136.108.4.250
Type
Hosting
Country
🇺🇸 United States
City
North Charleston
ISP
Google LLC
Organization
Google Cloud (us-east1)
Autonomous System
AS396982 Google LLC
Hit Count
47
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 7/2sAbnormally fast request rate — automated scanning+35
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 85
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-08-06 05:13:17
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 7/2s (+35), UA changed (+25)
2026-08-09 04:10:57
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

Google LLC
AS396982 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 136.108.4.250 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.108.4.0/24
  • 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 136.108.4.250 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 136.108.4.250.

🤖 User-Agent Anomaly Defense

IP 136.108.4.250 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

07

Neighbors in 136.108.4.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

136.108.4.250 has been assigned a threat score of 85/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 136.108.4.250 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. During its 2-day observation window, we recorded 47 hostile requests from this IP — roughly 23.5 per day on average. 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 129 flagged addresses, United States represents a significant presence in our threat database. At 85/100, this IP warrants immediate defensive action.

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.

11

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 →

🏢 Same network: AS396982

34.78.110.28 (348)136.67.84.210 (340)34.74.191.44 (340)136.67.103.22 (340)34.52.216.81 (313)View all →
12

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.

💡 Multi-Factor Authentication Importance

MFA dramatically reduces the effectiveness of credential-based attacks. Even when passwords are compromised through phishing or data breaches, the additional authentication factor prevents unauthorized access in the vast majority of cases.

🔍 Check Any IP Address

Share this report: