ABUSE.MOM
THREAT REPORT

IP Threat Report
136.85.26.126

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 13:47:16
First seen: 2026-08-08 23:54:47
Last seen: 2026-08-09 04:08:43
298

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODRATIO_404REFERERUA_CHANGED
01

Geolocation & Classification

IP Address
136.85.26.126
Type
Hosting
Country
🇸🇬 Singapore
City
Singapore
ISP
Google LLC
Organization
Google Cloud (asia-southeast1)
Autonomous System
AS396982 Google LLC
Hit Count
4
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 200/10sAbnormally fast request rate — automated scanning+35
Burst 66/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 7Medium-risk: admin panels, config files+60
Danger strong hits: 48High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 298
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-08-08 23:54:47
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 200/10s (+35), Burst 66/2s (+35)
2026-08-09 04:08:43
Last malicious request observed
Total score reached: 298/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇸🇬 Singapore
06

Recommendations

Actions taken & recommended

  • IP 136.85.26.126 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

🔎 Path Enumeration Protection

Block scanning from 136.85.26.126: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

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

🤖 User-Agent Anomaly Defense

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

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

10

Threat Analysis

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

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 136.85.26.126 to malicious activity originating from Singapore, Singapore, operating on the network of Google LLC. The address has been under observation since its initial detection. Our sensors captured 4 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~4 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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Singapore currently accounts for 133 blocked IPs in our database, making it a significant source of malicious traffic. At 298/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 Singapore

85.203.23.12 (340)103.167.150.231 (340)62.146.238.136 (340)85.203.23.31 (330)192.166.246.30 (325)View all →

🏢 Same network: AS396982

136.85.113.58 (298)34.126.144.14 (298)34.126.166.246 (298)136.85.67.167 (298)136.85.89.0 (298)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.

💡 Vulnerability Scanning Explained

Vulnerability scanning is the automated process of probing web applications for known weaknesses. Attackers use tools like Nuclei, Nikto, and ZAP to test thousands of hosts per hour, looking for exposed configuration files, outdated software, and default credentials.

🔍 Check Any IP Address

Share this report: