ABUSE.MOM
THREAT REPORT

IP Threat Report
136.65.82.2

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 01:50:22
First seen: 2026-09-10 23:55:37
Last seen: 2026-09-13 01:14:06
205

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
136.65.82.2
Type
Hosting
Country
🇺🇸 United States
City
Council Bluffs
ISP
Google LLC
Organization
Google Cloud (us-central1)
Autonomous System
AS396982 Google LLC
Hit Count
73
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 25/10sAbnormally fast request rate — automated scanning+35
Burst 25/2sAbnormally fast request rate — automated scanning+35
Burst 53/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 23High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 240
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-09-10 23:55:37
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 25/10s (+35), Burst 25/2s (+35), Burst 53/10s (+35)
2026-09-13 01:14:06
Last malicious request observed
Total score reached: 205/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇺🇸 United States

We have detected 8215 malicious IPs from this autonomous system.

View all IPs from AS396982 →
06

Recommendations

Actions taken & recommended

  • IP 136.65.82.2 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.65.82.2.

🤖 User-Agent Anomaly Defense

IP 136.65.82.2 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
b.barracudacentral.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com
✓ Clean
zen.spamhaus.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

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

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 136.65.82.2 has been traced to Council Bluffs, United States, operating on the network of Google LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 73 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~36.5 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 36,225 malicious IPs originating from United States, positioning it as a major contributor to global threat activity. With a threat score of 205/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.

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)35.254.195.37 (340)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.

💡 GraphQL Security Risks

GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.

🔍 Check Any IP Address

Share this report: