
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.
Block scanning from 198.245.68.48: 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 |
|---|---|---|---|
| 3128 | Unknown | Low | Service on port 3128 |
| 8000 | Unknown | Low | Service on port 8000 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| CVE ID | Link |
|---|---|
| CVE-2023-46846 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2018-1000027 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2019-12523 | NVD → |
| CVE-2019-12522 | NVD → |
| CVE-2019-12529 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2016-10002 | NVD → |
| CVE-2019-18860 | NVD → |
| CVE-2019-12524 | NVD → |
🔴 Security scanning identified 59 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.
198.245.68.48 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 198.245.68.48 to malicious activity originating from Buffalo, United States, operating on the network of B2 Net Solutions Inc.. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 80 flagged addresses, United States represents a notable presence in our threat database. A score of 105/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.
Modern HTTP protocols introduce new attack surfaces including stream multiplexing abuse, header compression attacks (HPACK bombing), and rapid reset attacks. Security tools must evolve to handle these protocol-specific threats effectively.