ABUSE.MOM
THREAT REPORT

IP Threat Report
173.230.135.36

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-06 01:22:59
First seen: 2026-08-30 22:02:59
Last seen: 2026-09-06 01:05:07
140

⛔ Verdict: BLOCK

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

BURSTRATIO_404REDIRECT_PROBEREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
173.230.135.36
Type
Hosting
Country
🇺🇸 United States
City
Atlanta
ISP
Akamai Technologies, Inc.
Organization
Linode
Autonomous System
AS63949 Akamai Connected Cloud
Hit Count
518
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 13/2sAbnormally fast request rate — automated scanning+35
Burst 14/10sAbnormally fast request rate — automated scanning+35
Burst 14/2sAbnormally fast request rate — automated scanning+35
Burst 7/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
Σ = 235
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-30 22:02:59
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Burst 13/2s (+35)
2026-09-06 01:05:07
Last malicious request observed
Total score reached: 140/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Akamai Technologies, Inc.
AS63949 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 173.230.135.36 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 173.230.135.36: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Traffic Flood Defense

IP 173.230.135.36 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 User-Agent Anomaly Defense

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

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

10

Threat Analysis

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

173.230.135.36 is registered in Atlanta, United States, operating on the network of Akamai Technologies, Inc.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 518 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~86.3 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 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 197 blocked IPs in our database, making it a significant source of malicious traffic. At 140/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 United States

104.28.246.115 (350)104.28.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS63949

104.64.217.139 (265)172.235.133.193 (240)97.107.128.157 (240)173.255.253.10 (240)172.232.164.94 (240)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.

💡 Insider Threat Indicators

Insider threats — whether malicious or negligent — account for a significant percentage of data breaches. Behavioral analytics detecting unusual access patterns, data downloads, and privilege escalation help identify insider risks before damage occurs.

🔍 Check Any IP Address

Share this report: