
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | 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 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 167.160.67.246 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 |
|---|---|---|---|
| 4444 | Unknown | Low | Service on port 4444 |
| 8000 | Unknown | Low | Service on port 8000 |
| 60000 | Unknown | Low | Service on port 60000 |
| CVE ID | Link |
|---|---|
| CVE-2023-49285 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2021-28652 | NVD → |
🔴 Security scanning identified 30 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.
167.160.67.246 has been assigned a threat score of 105/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 167.160.67.246 to malicious activity originating from Dallas, United States, operating on the network of Sprious LLC. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 200 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 105/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.
GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.