
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 7 | 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: 6 | 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.
Block scanning from 147.53.114.207: 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-2021-28652 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2023-50269 | 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.53.114.207 has been assigned a threat score of 105/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
Threat intelligence analysis has linked 147.53.114.207 to malicious activity originating from Pittsburgh, United States, operating on the network of Blazing SEO. The address has been under observation since its initial detection. Our sensors captured 3 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 201 blocked IPs in our database, making it a significant source of malicious traffic. At 105/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.