
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger medium hits: 12 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Imported from old blocklist | Behavioral anomaly detected by automated analysis | +0 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 23.160.128.49 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Block scanning from 23.160.128.49: 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 |
|---|---|---|---|
| 4444 | Unknown | Low | Service on port 4444 |
| 8000 | Unknown | Low | Service on port 8000 |
| CVE ID | Link |
|---|---|
| CVE-2025-62168 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2024-25111 | NVD → |
🔴 Security scanning identified 27 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.
23.160.128.49 has been assigned a threat score of 130/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
IP address 23.160.128.49 has been traced to Los Angeles, United States, operating on the network of Sprious LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 33 malicious requests from this address across a 54-day span, reflecting a sustained attack cadence of ~0.6 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 206 blocked IPs in our database, making it a significant source of malicious traffic. At 130/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.