IP Threat Report
31.129.47.28
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: curl | Known bot/crawler User-Agent detected | +40 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 |
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 31.129.47.28 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
🤖 Bot Detection
Address UA spoofing from 31.129.47.28: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Directory Scan Defense
IP 31.129.47.28 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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 |
| 465 | Unknown | Low | Service on port 465 |
| 2222 | Unknown | Low | Service on port 2222 |
| 3001 | Unknown | Low | Service on port 3001 |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8443 | HTTPS-Alt | Low | Service on port 8443 |
⚠️ Network scanning reveals 1 dangerous service exposed on 31.129.47.28. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2025-50084 | NVD → |
| CVE-2025-50094 | NVD → |
| CVE-2025-67896 | NVD → |
| CVE-2022-3559 | NVD → |
| CVE-2025-30232 | NVD → |
| CVE-2025-50092 | NVD → |
| CVE-2025-50078 | NVD → |
| CVE-2025-50087 | NVD → |
| CVE-2023-42115 | NVD → |
| CVE-2023-42119 | NVD → |
| CVE-2025-50098 | NVD → |
| CVE-2025-50097 | NVD → |
| CVE-2025-50077 | NVD → |
| CVE-2025-50091 | NVD → |
| CVE-2025-50093 | NVD → |
| CVE-2025-50076 | NVD → |
| CVE-2025-50080 | NVD → |
| CVE-2025-50079 | NVD → |
| CVE-2025-50083 | NVD → |
| CVE-2025-50099 | NVD → |
| CVE-2024-39929 | NVD → |
| CVE-2026-21964 | NVD → |
| CVE-2023-42114 | NVD → |
| CVE-2025-50081 | NVD → |
| CVE-2025-50082 | NVD → |
🔴 This host has 36 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
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
31.129.47.28 has been assigned a threat score of 65/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.
The following attack categories were identified:
📊 Threat Analysis
The address 31.129.47.28 originates from Moscow, Russia, operating on the network of JSC Selectel. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 1-day observation window, we recorded 3 hostile requests from this IP — roughly 3 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 dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. With 140 flagged addresses, Russia represents a significant presence in our threat database. At 65/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
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
Security Intelligence
💡 HTTP Header Analysis for Threat Detection
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
💡 Security Header Best Practices
HTTP security headers provide defense-in-depth with minimal implementation effort. Key headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy, each addressing specific attack vectors.