
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.
IP 156.241.212.148 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8800 | Unknown | Low | Service on port 8800 |
| CVE ID | Link |
|---|---|
| CVE-2023-46728 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2024-23638 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-46848 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2024-37894 | NVD → |
🔴 Security scanning identified 24 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.
156.241.212.148 has been assigned a threat score of 105/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
Threat intelligence analysis has linked 156.241.212.148 to malicious activity originating from Miami, United States, operating on the network of DynaNode LLC. The address has been under observation since its initial detection. During its 10-day observation window, we recorded 2 hostile requests from this IP — roughly 0.2 per day on average. 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 198 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 105/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.
Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.