
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 20 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 31 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 55 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 54 | Medium-risk: admin panels, config files | +60 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 37 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 55 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 216.126.227.102.
Block scanning from 216.126.227.102: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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 |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| CVE ID | Link |
|---|---|
| CVE-2025-49812 | NVD → |
| CVE-2024-43394 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2009-2299 | NVD → |
| CVE-2025-49630 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2013-0941 | NVD → |
| CVE-2025-66200 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2025-23048 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2012-4360 | NVD → |
| CVE-2025-55753 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2024-42516 | NVD → |
| CVE-2024-43204 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2025-65082 | NVD → |
| CVE-2024-47252 | NVD → |
| CVE-2012-4001 | NVD → |
| CVE-2012-3526 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2025-53020 | NVD → |
| CVE-2007-4723 | NVD → |
🔴 Security scanning identified 25 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.
216.126.227.102 has been assigned a threat score of 195/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 intelligence analysis has linked 216.126.227.102 to malicious activity originating from Ogden, United States, operating on the network of RouterHosting LLC. The address has been under observation since its initial detection. Our sensors captured 3 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~3 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Request Flooding combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. With 33 flagged addresses, United States represents a notable presence in our threat database. At 195/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.
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.
Certificate Transparency logs record all publicly trusted TLS certificates. Monitoring these logs reveals unauthorized certificate issuance, phishing domain preparation, and shadow IT — providing early warning of attacks targeting an organizations domain.