ABUSE.MOM
THREAT REPORT

IP Threat Report
35.208.53.77

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 00:57:12
First seen: 2026-05-04 10:00:07
Last seen: 2026-05-04 10:00:07
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 10 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 11 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 80
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-04 10:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 10 req / 2s (+35), Burst: 11 req / 10s (+35), Foreign referer seen (+10)
2026-05-04 10:00:07
Last malicious request observed
Total score reached: 80/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS15169 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 35.208.53.77 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.208.53.77.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (1)
PortServiceRiskDescription
80HTTPLowHTTP web server — standard web traffic
DETECTED TECHNOLOGIES
google:cloud_platform
Hostnames: 77.53.208.35.bc.googleusercontent.com
PTR: 77.53.208.35.bc.googleusercontent.com

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

35.208.53.77 has been assigned a threat score of 80/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 Flooding

📊 Threat Analysis

Network traffic from 35.208.53.77, located in Council Bluffs, United States, operating on the network of Google LLC, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per 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. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 201 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. The score of 80/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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: AS15169

66.249.82.32 (205)74.125.217.40 (175)192.178.11.96 (170)35.212.230.168 (170)209.85.238.2 (165)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.

💡 Content Delivery Network Risks

CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.

🔍 Check Any IP Address

Share this report: