ABUSE.MOM
THREAT REPORT

IP Threat Report
136.107.239.70

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 23:10:54
First seen: 2026-05-21 22:32:56
Last seen: 2026-05-24 08:40:03
105

⛔ Verdict: BLOCK

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

BURSTREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
136.107.239.70
Type
Hosting
Country
🇺🇸 United States
City
Washington
ISP
Google LLC
Organization
Google Cloud (us-east4)
Autonomous System
AS396982 Google LLC
Hit Count
59
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 20/2sAbnormally fast request rate — automated scanning+35
Burst 21/10sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 105
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-05-21 22:32:56
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 20/2s (+35), Burst 21/10s (+35), Foreign referer (+10)
2026-05-24 08:40:03
Last malicious request observed
Total score reached: 105/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.107.239.70 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.107.239.70.

🤖 Bot Detection

Address UA spoofing from 136.107.239.70: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

136.107.239.70 has been assigned a threat score of 105/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

Threat intelligence analysis has linked 136.107.239.70 to malicious activity originating from Washington, United States, operating on the network of Google LLC. The address has been under observation since its initial detection. The address has been active for 2 days in our monitoring system, producing 59 flagged requests at a rate of ~29.5/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 140 flagged addresses, United States represents a significant presence in our threat database. A score of 105/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.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS396982

34.187.158.4 (340)34.186.187.208 (340)34.136.84.236 (288)35.254.215.135 (288)35.243.110.60 (288)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.

💡 Autonomous System Analysis

Analyzing attack patterns at the AS (Autonomous System) level reveals which networks harbor the most malicious activity. Some ASes have abuse rates orders of magnitude higher than average, indicating lax enforcement of acceptable use policies.

🔍 Check Any IP Address

Share this report: