
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 66 | Medium-risk: admin panels, config files | +60 | |
| Burst: 128 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 173 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger medium hits: 79 | Medium-risk: admin panels, config files | +60 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 183 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 200 req / 10s | Abnormally fast request rate — automated scanning | +35 |
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 89.108.117.128.
IP 89.108.117.128 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
IP 89.108.117.128 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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 |
| 9090 | Unknown | Low | Service on port 9090 |
| 10050 | Unknown | Low | Service on port 10050 |
| CVE ID | Link |
|---|---|
| CVE-2020-14145 | NVD → |
| CVE-2019-9516 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2019-16905 | NVD → |
| CVE-2020-7069 | NVD → |
| CVE-2019-11042 | NVD → |
| CVE-2022-4900 | NVD → |
| CVE-2019-11045 | NVD → |
| CVE-2017-8923 | NVD → |
| CVE-2020-7070 | NVD → |
| CVE-2007-3205 | NVD → |
| CVE-2019-13224 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2024-3566 | NVD → |
| CVE-2019-11038 | NVD → |
| CVE-2018-16845 | NVD → |
| CVE-2022-31629 | NVD → |
| CVE-2019-9511 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2019-11050 | NVD → |
| CVE-2019-11039 | NVD → |
| CVE-2020-7059 | NVD → |
| CVE-2019-11041 | NVD → |
| CVE-2020-7068 | NVD → |
🔴 Security scanning identified 62 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.
89.108.117.128 has been assigned a threat score of 185/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
IP address 89.108.117.128 has been traced to Moscow, Russia, operating on the network of "Domain names registrar REG.RU", Ltd. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 46-day observation window, we recorded 2 hostile requests from this IP — roughly 0 per day on average. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Russia currently accounts for 111 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 185/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.
Cache poisoning manipulates web cache behavior to serve malicious content to other users. By identifying unkeyed inputs that influence cached responses, attackers can inject JavaScript, redirect users, or cause denial of service at scale through the cache infrastructure.