
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: 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 | |
| Danger medium hits: 7 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 147.92.52.213 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Block scanning from 147.92.52.213: 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 |
|---|---|---|---|
| 8000 | Unknown | Low | Service on port 8000 |
| 60000 | Unknown | Low | Service on port 60000 |
| CVE ID | Link |
|---|---|
| CVE-2024-45802 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2025-62168 | 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.
147.92.52.213 has been assigned a threat score of 130/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 147.92.52.213 to malicious activity originating from Los Angeles, United States, operating on the network of Sprious LLC, Emeigh Investments LLC. The address has been under observation since its initial detection. Our sensors captured 4 malicious requests from this address across a 18-day span, reflecting a sustained attack cadence of ~0.2 requests per 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 dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. With 206 flagged addresses, United States represents a significant presence in our threat database. 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.
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.
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.