IP Threat Report
128.173.237.154
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Burst: 5 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 128.173.237.154 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
🔎 Directory Scan Defense
IP 128.173.237.154 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 128.173.237.154.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 2222 | Unknown | Low | Service on port 2222 |
| 3000 | Unknown | Low | Service on port 3000 |
| 3333 | Unknown | Low | Service on port 3333 |
| 5432 | PostgreSQL | High | PostgreSQL database — direct database access risk |
| 5435 | Unknown | Low | Service on port 5435 |
| 6379 | Redis | Critical | Redis in-memory database — frequently misconfigured without auth |
| 18081 | Unknown | Low | Service on port 18081 |
⚠️ Network scanning reveals 2 dangerous services exposed on 128.173.237.154. Open database ports suggest possible data exfiltration risk. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2022-31777 | NVD → |
| CVE-2021-38296 | NVD → |
| CVE-2019-10172 | NVD → |
| CVE-2025-4123 | NVD → |
| CVE-2026-21722 | NVD → |
| CVE-2022-33891 | NVD → |
| CVE-2024-1442 | NVD → |
| CVE-2020-11023 | NVD → |
| CVE-2024-23945 | NVD → |
| CVE-2020-11022 | NVD → |
| CVE-2025-55039 | NVD → |
| CVE-2018-17190 | NVD → |
| CVE-2023-22946 | NVD → |
| CVE-2026-21720 | NVD → |
| CVE-2023-32007 | NVD → |
| CVE-2023-6152 | NVD → |
🔴 Security scanning identified 16 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
128.173.237.154 has been assigned a threat score of 60/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
The following attack categories were identified:
📊 Threat Analysis
Our monitoring infrastructure has identified 128.173.237.154, geolocated to Blacksburg, United States, operating on the network of Virginia Polytechnic Institute and State Univ., as a source of suspicious network activity. During its 55-day observation window, we recorded 20 hostile requests from this IP — roughly 0.4 per day on average. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
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.
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 →🏢 Same network: AS1312
View all →Security Intelligence
💡 DDoS Mitigation Approaches
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
💡 BGP Hijacking and IP Spoofing
Border Gateway Protocol hijacking allows attackers to redirect internet traffic through their infrastructure. While less common than application-level attacks, BGP hijacks can intercept sensitive data, inject malware, or cause widespread service disruption.