ABUSE.MOM
THREAT REPORT

IP Threat Report
34.61.130.139

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 21:43:50
First seen: 2026-05-17 15:00:06
Last seen: 2026-05-24 10:08:40
155

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 16/2sAbnormally fast request rate — automated scanning+35
Burst 21/10sAbnormally fast request rate — automated scanning+35
Burst: 16 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 21 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 19Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Σ = 235
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-17 15:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 16/2s (+35), Burst 21/10s (+35), Burst: 16 req / 2s (+35)
2026-05-24 10:08:40
Last malicious request observed
Total score reached: 155/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 34.61.130.139 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

🌊 Traffic Flood Defense

IP 34.61.130.139 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

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

Request Flooding

📊 Threat Analysis

The address 34.61.130.139 originates from Council Bluffs, United States, operating on the network of Google LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 6-day observation window, we recorded 245 hostile requests from this IP — roughly 40.8 per day on average. 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 IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. United States currently accounts for 140 blocked IPs in our database, making it a significant source of malicious traffic. At 155/100, this is an extremely high-risk address. All traffic should be considered hostile.

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.

💡 BGP Hijacking and IP Spoofing

Border Gateway Protocol hijacking allows attackers to redirect internet traffic through their infrastructure. While less common than application-level attacks, BGP hijacks can intercept sensitive data, inject malware, or cause widespread service disruption.

🔍 Check Any IP Address

Share this report: