
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 8 | 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 156.241.194.208: 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 |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 3128 | Unknown | Low | Service on port 3128 |
| CVE ID | Link |
|---|---|
| CVE-2022-41318 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2024-23638 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2023-46848 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2024-25617 | 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.194.208 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 156.241.194.208 to malicious activity originating from New York, United States, operating on the network of DynaNode LLC. The address has been under observation since its initial detection. 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 198 flagged addresses, United States represents a significant presence in our threat database. 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.
WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.
Open redirect vulnerabilities allow attackers to redirect users from trusted domains to malicious sites. While often underestimated, these flaws enable convincing phishing, token theft through redirect-based OAuth flows, and SSRF chains.