ABUSE.MOM
THREAT REPORT

IP Threat Report
35.254.33.191

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 21:45:43
First seen: 2026-05-17 17:00:06
Last seen: 2026-05-24 10:10:51
155

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

IP Address
35.254.33.191
Type
Hosting
Country
🇺🇸 United States
City
Council Bluffs
ISP
Google LLC
Organization
Google Cloud (us-central1)
Autonomous System
AS396982 Google LLC
Hit Count
213
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 17: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:10:51
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 35.254.33.191 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 35.254.33.191.

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
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
cbl.abuseat.org
✓ Clean
psbl.surriel.com
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

35.254.33.191 has been assigned a threat score of 155/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Network traffic from 35.254.33.191, located in Council Bluffs, United States, operating on the network of Google LLC, has been classified as malicious by our automated threat scoring engine. Our sensors captured 213 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~35.5 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. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. With 140 flagged addresses, United States represents a significant presence in our threat database. A score of 155/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.

💡 Web Cache Poisoning Attacks

Cache poisoning manipulates web cache behavior to serve malicious content to other users. By identifying unkeyed inputs that influence cached responses, attackers can inject JavaScript, redirect users, or cause denial of service at scale through the cache infrastructure.

🔍 Check Any IP Address

Share this report: