IP Threat Report
172.235.33.38
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 16 | Medium-risk: admin panels, config files | +60 | |
| Burst: 14 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 16 req / 10s | Abnormally fast request rate — automated scanning | +35 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 172.235.33.38 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
🌊 Traffic Flood Defense
IP 172.235.33.38 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 3389 | RDP | High | Remote Desktop Protocol — primary target for ransomware attacks |
⚠️ Network scanning reveals 1 dangerous service exposed on 172.235.33.38. Exposed RDP (3389) is the #1 entry point for ransomware attacks. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2011-3182 | NVD → |
| CVE-2014-3515 | NVD → |
| CVE-2015-1351 | NVD → |
| CVE-2011-4415 | NVD → |
| CVE-2012-2311 | NVD → |
| CVE-2016-10161 | NVD → |
| CVE-2016-6289 | NVD → |
| CVE-2019-9639 | NVD → |
| CVE-2010-1914 | NVD → |
| CVE-2018-17082 | NVD → |
| CVE-2009-4017 | NVD → |
| CVE-2011-4317 | NVD → |
| CVE-2015-3412 | NVD → |
| CVE-2009-3291 | NVD → |
| CVE-2016-6296 | NVD → |
| CVE-2016-9934 | NVD → |
| CVE-2014-9427 | NVD → |
| CVE-2015-3330 | NVD → |
| CVE-2013-6501 | NVD → |
| CVE-2014-8626 | NVD → |
| CVE-2017-9224 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2016-7478 | NVD → |
| CVE-2015-8935 | NVD → |
| CVE-2015-6831 | NVD → |
🔴 This host has 389 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
172.235.33.38 has been assigned a threat score of 155/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
The address 172.235.33.38 originates from Los Angeles, United States, operating on the network of Akamai Technologies, Inc.. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/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 IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. Our records show 32 malicious IPs originating from United States, positioning it as a notable contributor to global threat activity. A score of 155/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.
Related Threats
🇺🇸 Top threats from United States
50.116.47.11 (255)45.33.70.9 (230)74.207.234.150 (230)172.232.29.203 (180)172.232.15.40 (155)View all →Security Intelligence
💡 WordPress-Specific Attack Vectors
WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.
💡 Emerging Threats from AI-Powered Attacks
Artificial intelligence enables more convincing phishing content, faster vulnerability discovery, and adaptive attack strategies that learn from defensive responses. AI-generated social engineering and automated exploit development represent growing threats.