ABUSE.MOM
THREAT REPORT

IP Threat Report
35.185.143.111

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 12:08:01
First seen: 2026-05-20 12:35:26
Last seen: 2026-05-24 07:48:09
200

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 9/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 4Medium-risk: admin panels, config files+40
Danger strong hits: 7High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
Σ = 200
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-20 12:35:26
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 9/2s (+35), Danger medium hits: 4 (+40)
2026-05-24 07:48:09
Last malicious request observed
Total score reached: 200/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.185.143.111 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

🔎 Directory Scan Defense

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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 35.185.143.111.

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

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

10

Threat Analysis

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

Path EnumerationRequest Flooding

📊 Threat Analysis

Network traffic from 35.185.143.111, located in Taipei, Taiwan, operating on the network of Google LLC, has been classified as malicious by our automated threat scoring engine. Over a period of 3 days, this IP generated 133 malicious requests, averaging approximately 44.3 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 71 flagged addresses, Taiwan represents a notable presence in our threat database. At 200/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 Taiwan

34.80.73.228 (253)34.80.216.128 (195)104.155.218.51 (180)35.234.32.129 (180)34.80.45.141 (155)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.

💡 GeoIP Blocking Considerations

Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.

🔍 Check Any IP Address

Share this report: