
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| POST requests present | Behavioral anomaly detected by automated analysis | +8 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 201.174.234.34 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 201.174.234.34 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 53 | DNS | Low | DNS server — potential for DNS amplification attacks |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 81 | Unknown | Low | Service on port 81 |
| 84 | Unknown | Low | Service on port 84 |
| 123 | Unknown | Low | Service on port 123 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 1027 | Unknown | Low | Service on port 1027 |
| 1701 | Unknown | Low | Service on port 1701 |
| 8282 | Unknown | Low | Service on port 8282 |
| 9090 | Unknown | Low | Service on port 9090 |
| CVE ID | Link |
|---|---|
| CVE-2021-32792 | NVD → |
| CVE-2006-20001 | NVD → |
| CVE-2018-7185 | NVD → |
| CVE-2019-11039 | NVD → |
| CVE-2024-43204 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2018-14851 | NVD → |
| CVE-2022-22719 | NVD → |
| CVE-2020-1934 | NVD → |
| CVE-2015-3185 | NVD → |
| CVE-2016-7434 | NVD → |
| CVE-2019-0217 | NVD → |
| CVE-2017-8923 | NVD → |
| CVE-2018-12882 | NVD → |
| CVE-2016-8743 | NVD → |
| CVE-2019-11044 | NVD → |
| CVE-2024-38472 | NVD → |
| CVE-2015-7692 | NVD → |
| CVE-2014-9751 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2015-5146 | NVD → |
| CVE-2022-31629 | NVD → |
| CVE-2022-31628 | NVD → |
| CVE-2019-11041 | NVD → |
| CVE-2020-7067 | NVD → |
🔴 Security scanning identified 236 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.
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.
201.174.234.34 has been assigned a threat score of 128/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:
Threat intelligence analysis has linked 201.174.234.34 to malicious activity originating from Tijuana, Mexico, operating on the network of Transtelco Inc. The address has been under observation since its initial detection. During its 5-day observation window, we recorded 3 hostile requests from this IP — roughly 0.6 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Mexico currently accounts for 122 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 128/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.
Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.