
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 14 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| 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.
Address UA spoofing from 118.219.255.169: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 118.219.255.169.
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 |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 111 | Unknown | Low | Service on port 111 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 2222 | Unknown | Low | Service on port 2222 |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
| 8009 | Unknown | Low | Service on port 8009 |
⚠️ Network scanning reveals 2 dangerous services exposed on 118.219.255.169. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2023-0464 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2019-2757 | NVD → |
| CVE-2017-3645 | NVD → |
| CVE-2017-3251 | NVD → |
| CVE-2019-10092 | NVD → |
| CVE-2019-2738 | NVD → |
| CVE-2020-7062 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2025-68160 | NVD → |
| CVE-2016-0736 | NVD → |
| CVE-2020-14793 | NVD → |
| CVE-2016-5634 | NVD → |
| CVE-2017-10165 | NVD → |
| CVE-2019-2730 | NVD → |
| CVE-2020-7061 | NVD → |
| CVE-2018-3061 | NVD → |
| CVE-2024-24795 | NVD → |
| CVE-2017-10167 | NVD → |
| CVE-2013-5704 | NVD → |
| CVE-2021-2022 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2019-1559 | NVD → |
| CVE-2013-4352 | NVD → |
| CVE-2017-3319 | NVD → |
🔴 This host has 325 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.
118.219.255.169 has been assigned a threat score of 220/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:
The address 118.219.255.169 originates from Hwaseong-si, South Korea, operating on the network of SK Broadband Co Ltd. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Two attack patterns were identified (User-Agent Anomaly and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 102 flagged addresses, South Korea represents a significant presence in our threat database. A score of 220/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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
VPN exit nodes aggregate traffic from many users, creating mixed reputation profiles. While legitimate users seek privacy, attackers exploit VPN services to anonymize malicious activity, making IP-based blocking of VPN nodes a complex policy decision.