
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| 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 162.244.144.140: 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-2022-41318 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2025-59362 | 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.
162.244.144.140 has been assigned a threat score of 70/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
The following attack categories were identified:
IP address 162.244.144.140 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. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. United States currently accounts for 201 blocked IPs in our database, making it a significant source of malicious traffic. A threat score of 70/100 places this IP in the high-risk category. Blocking at the firewall level is 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.
Email authentication protocols work together to prevent spoofing. SPF validates sending servers, DKIM provides cryptographic message signing, and DMARC defines enforcement policies. Full implementation significantly reduces phishing effectiveness.