
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 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 |
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 61.72.221.194: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 1723 | PPTP | Low | Service on port 1723 |
| 3128 | Unknown | Low | Service on port 3128 |
| CVE ID | Link |
|---|---|
| CVE-2025-54574 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2020-11945 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2020-15811 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2021-31807 | NVD → |
🔴 This host has 35 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
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.
61.72.221.194 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:
61.72.221.194 is registered in Seongnam-si, South Korea, operating on the network of Korea Telecom. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 4 days in our monitoring system, producing 3 flagged requests at a rate of ~0.8/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. South Korea currently accounts for 146 blocked IPs in our database, making it a significant source of malicious traffic. 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.
Edge computing pushes processing closer to users but expands the attack surface. Edge nodes often run in less secure environments than centralized data centers, creating new opportunities for physical access attacks and supply chain compromises.
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.