
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 147.53.121.190: 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 |
| CVE ID | Link |
|---|---|
| CVE-2026-32748 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-49286 | NVD → |
🔴 This host has 30 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
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.53.121.190 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:
147.53.121.190 is registered in Dallas, United States, operating on the network of Blazing SEO. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~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. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 204 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 105/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.
RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.
Containerized applications face unique security challenges including vulnerable base images, excessive privileges, shared kernel attacks, and insecure orchestration configurations. Runtime security monitoring and immutable container policies mitigate these risks.