ABUSE.MOM
THREAT REPORT

IP Threat Report
136.108.35.236

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-08-23 20:28:18
First seen: 2026-08-21 10:10:18
Last seen: 2026-08-23 02:03:19
273

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODREFERERUA_CHANGED
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 185/2sAbnormally fast request rate — automated scanning+35
Burst 200/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 14Medium-risk: admin panels, config files+60
Danger medium hits: 21Medium-risk: admin panels, config files+60
Danger strong hits: 131High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 77High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 433
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-21 10:10:18
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 185/2s (+35), Burst 200/10s (+35), Danger medium hits: 14 (+60)
2026-08-23 02:03:19
Last malicious request observed
Total score reached: 273/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.35.236 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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 136.108.35.236.

🤖 User-Agent Anomaly Defense

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

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

136.108.35.236 has been assigned a threat score of 273/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:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 136.108.35.236, geolocated to North Charleston, United States, operating on the network of Google LLC, as a source of suspicious network activity. Over a period of 1 days, this IP generated 55 malicious requests, averaging approximately 55 requests per 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. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 128 blocked IPs in our database, making it a significant source of malicious traffic. A score of 273/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.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS396982

136.67.84.210 (340)34.74.191.44 (340)136.67.103.22 (340)34.52.216.81 (313)136.66.254.33 (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.

💡 Insider Threat Indicators

Insider threats — whether malicious or negligent — account for a significant percentage of data breaches. Behavioral analytics detecting unusual access patterns, data downloads, and privilege escalation help identify insider risks before damage occurs.

🔍 Check Any IP Address

Share this report: