IP Threat Report
172.182.224.193
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
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.182.224.193 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 172.182.224.0/24
- 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 172.182.224.193: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🤖 Bot Detection
Address UA spoofing from 172.182.224.193: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Neighbors in 172.182.224.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.182.224.193 has been assigned a threat score of 153/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.182.224.193 originates from Phoenix, United States, operating on the network of Microsoft. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 21 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~21 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 103 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 153/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
104.28.246.115 (350)104.28.214.122 (350)103.215.74.213 (340)103.168.66.237 (340)34.187.158.4 (340)View all →Security Intelligence
💡 Prototype Pollution Attacks
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.
💡 Edge Computing Attack Surface
Edge computing pushes processing closer to users but expands the attack surface. Edge nodes often run in less secure environments than centralized data centers, creating new opportunities for physical access attacks and supply chain compromises.