
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 |
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 142.147.108.203: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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-2021-28116 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2023-46728 | 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.
142.147.108.203 has been assigned a threat score of 105/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
IP address 142.147.108.203 has been traced to Los Angeles, United States, operating on the network of Sprious LLC, Blazing SEO, LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 76 days in our monitoring system, producing 9 flagged requests at a rate of ~0.1/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 202 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.
Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.
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.