
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| 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 |
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 141.164.86.79: 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-2024-45802 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2021-28662 | 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.
141.164.86.79 has been assigned a threat score of 105/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 141.164.86.79 to malicious activity originating from Los Angeles, United States, operating on the network of Sprious LLC. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 2 flagged requests at a rate of ~2/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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 205 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. 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.
CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.