ABUSE.MOM
THREAT REPORT

IP Threat Report
172.237.156.107

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 01:58:31
First seen: 2026-08-01 18:26:39
Last seen: 2026-08-02 00:54:25
225

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
172.237.156.107
Type
Hosting
Country
🇺🇸 United States
City
Chicago
ISP
Akamai Technologies, Inc.
Organization
Akamai Technologies, Inc.
Autonomous System
AS63949 Akamai Connected Cloud
Hit Count
14
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 31/10sAbnormally fast request rate — automated scanning+35
Burst 31/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 225
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-01 18:26:39
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 31/10s (+35), Burst 31/2s (+35), Danger medium hits: 2 (+20)
2026-08-02 00:54:25
Last malicious request observed
Total score reached: 225/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 172.237.156.107 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 172.237.156.107.

🤖 User-Agent Anomaly Defense

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

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

10

Threat Analysis

172.237.156.107 has been assigned a threat score of 225/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Network traffic from 172.237.156.107, located in Chicago, United States, operating on the network of Akamai Technologies, Inc., has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 14 malicious requests, averaging approximately 14 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. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 195 blocked IPs in our database, making it a significant source of malicious traffic. At 225/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.

💡 Rate Limiting and Throttling Strategies

Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.

🔍 Check Any IP Address

Share this report: