
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 221.168.44.67 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Address UA spoofing from 221.168.44.67: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 21 | FTP | Medium | File Transfer Protocol — often targeted for anonymous login attacks |
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 123 | Unknown | Low | Service on port 123 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 500 | Unknown | Low | Service on port 500 |
⚠️ 1 high-risk port detected on 221.168.44.67. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2021-41617 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2018-20685 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2020-14145 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2019-6111 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2018-15919 | NVD → |
| CVE-2017-15906 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2019-6110 | NVD → |
| CVE-2019-6109 | NVD → |
| CVE-2018-15473 | NVD → |
🔴 This host has 20 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.
221.168.44.67 has been assigned a threat score of 95/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
Network traffic from 221.168.44.67, located in Seodaemun-gu, South Korea, operating on the network of Korea Telecom, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 4 hostile requests from this IP — roughly 4 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 146 malicious IPs originating from South Korea, positioning it as a significant contributor to global threat activity. A score of 95/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.
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.
Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.