
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 | |
| Imported from old blocklist | Behavioral anomaly detected by automated analysis | +0 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger medium hits: 8 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 148.59.146.32 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 148.59.146.32 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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-54574 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2023-49288 | 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.
148.59.146.32 has been assigned a threat score of 130/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
IP address 148.59.146.32 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. During its 56-day observation window, we recorded 31 hostile requests from this IP — roughly 0.6 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 202 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 130/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.
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.