ABUSE.MOM
THREAT REPORT

IP Threat Report
35.189.172.222

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:55:06
First seen: 2026-07-01 11:42:29
Last seen: 2026-07-05 03:51:17
180

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

IP Address
35.189.172.222
Type
Hosting
Country
🇹🇼 Taiwan
City
Taipei
ISP
Google LLC
Organization
Google Cloud (asia-east1)
Autonomous System
AS396982 Google LLC
Hit Count
282
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 26/10sAbnormally fast request rate — automated scanning+35
Burst 7/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 44High-risk paths: shells, RCE vectors, exploits+100
Σ = 205
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-07-01 11:42:29
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 26/10s (+35), Burst 7/2s (+35), Danger medium hits: 1 (+10)
2026-07-05 03:51:17
Last malicious request observed
Total score reached: 180/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇹🇼 Taiwan
06

Recommendations

Actions taken & recommended

  • IP 35.189.172.222 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.189.172.222.

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

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

10

Threat Analysis

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

The address 35.189.172.222 originates from Taipei, Taiwan, operating on the network of Google LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 282 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~94 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. Taiwan currently accounts for 12 blocked IPs in our database, making it a notable source of malicious traffic. A score of 180/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 Taiwan

34.81.125.215 (298)35.201.233.251 (288)35.229.166.149 (195)34.81.169.179 (195)35.201.195.226 (195)View all →

🏢 Same network: AS396982

136.67.84.210 (340)34.74.191.44 (340)136.67.103.22 (340)136.66.254.33 (313)34.52.216.81 (313)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.

💡 Automated Incident Response

Automated response systems can block threats in milliseconds, far faster than human analysts. However, automation requires careful safeguards — rate limits on blocking actions, automatic expiration, and human review queues prevent automated systems from causing self-inflicted outages.

🔍 Check Any IP Address

Share this report: