IP Threat Report
34.182.3.226
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: 19 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 17 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 21 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 15 req / 2s | 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 34.182.3.226 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 34.182.3.226: 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 34.182.3.226.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 32764 | Unknown | Low | Service on port 32764 |
| CVE ID | Link |
|---|---|
| CVE-2024-9287 | NVD → |
| CVE-2019-9674 | NVD → |
| CVE-2022-45061 | NVD → |
| CVE-2022-48565 | NVD → |
| CVE-2022-26488 | NVD → |
| CVE-2020-14422 | NVD → |
| CVE-2020-27619 | NVD → |
| CVE-2021-28861 | NVD → |
| CVE-2023-36632 | NVD → |
| CVE-2020-8492 | NVD → |
| CVE-2024-6232 | NVD → |
| CVE-2026-27205 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2025-12084 | NVD → |
| CVE-2021-3426 | NVD → |
| CVE-2022-48566 | NVD → |
| CVE-2020-8315 | NVD → |
| CVE-2007-4559 | NVD → |
| CVE-2023-27043 | NVD → |
| CVE-2020-29396 | NVD → |
| CVE-2019-18348 | NVD → |
| CVE-2013-0340 | NVD → |
| CVE-2019-16935 | NVD → |
| CVE-2021-3177 | NVD → |
| CVE-2024-7592 | NVD → |
🔴 Security scanning identified 53 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
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
34.182.3.226 has been assigned a threat score of 180/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:
📊 Threat Analysis
Threat intelligence analysis has linked 34.182.3.226 to malicious activity originating from The Dalles, United States, operating on the network of Google LLC. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 2 flagged requests at a rate of ~2/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 (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 142 flagged addresses, United States represents a significant presence in our threat database. A score of 180/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.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →Security Intelligence
💡 Server-Side Request Forgery (SSRF)
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.
💡 Network Segmentation Benefits
Proper network segmentation limits the blast radius of breaches. Even if attackers compromise one segment, properly configured network boundaries prevent lateral movement to critical systems, databases, and administrative interfaces.