ABUSE.MOM
THREAT REPORT

IP Threat Report
35.196.51.213

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 22:21:44
First seen: 2026-05-21 01:26:40
Last seen: 2026-05-24 09:51:44
125

⛔ Verdict: BLOCK

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

BURSTREDIRECT_PROBEREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
35.196.51.213
Type
Hosting
Country
🇺🇸 United States
City
North Charleston
ISP
Google LLC
Organization
Google Cloud (us-east1)
Autonomous System
AS396982 Google LLC
Hit Count
139
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 14/10sAbnormally fast request rate — automated scanning+35
Burst 14/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 125
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 01:26:40
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 14/10s (+35), Burst 14/2s (+35), Foreign referer (+10)
2026-05-24 09:51:44
Last malicious request observed
Total score reached: 125/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.196.51.213 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.196.51.213.

🔎 Directory Scan Defense

IP 35.196.51.213 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 User-Agent Anomaly Defense

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

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

10

Threat Analysis

35.196.51.213 has been assigned a threat score of 125/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request FloodingPath EnumerationUser-Agent Anomaly

📊 Threat Analysis

The address 35.196.51.213 originates from North Charleston, United States, operating on the network of Google LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 3 days, this IP generated 139 malicious requests, averaging approximately 46.3 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 diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. United States currently accounts for 140 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 125/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.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.

💡 Server-Side Template Injection

SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.

🔍 Check Any IP Address

Share this report: